Need help using a query rule with a DB2 database running on a Linux server.

That has to do with the way the library used for query rules work. Here's what you need to do:

APPROACH #1:

1. Change the schema name that owns this view to be lowercase.
2. Edit your XSD to use the schema="" attribute and put the schema name in lower case

@Table(name="" schema="")

3. Delete the CDT
4. Re-upload the updated CDT
5. Run impact analysis to update your data store (assuming the Data store is inside an application)
6. Update the data store

APPROACH #2

If you cannot rename it to lowercase (which is the default behavior of Appian for DS validation) then you will have to do this:

In DB2:

1. Login as the SCHEMA who owns the view
2. Grant privileges over the VIEW to the Appian ID
3. Login as the Appian ID
4. Create a synonym where XXXXX is the Schema that owns the view


CREATE SYNONYM UPS_ORGHIERARCHY FOR XXXXX.UPS_ORGHIERARCHY;

5. Make sure your XSD has the following annotation WITHOUT ANYT SCHEMA NAME

@Table(name="UPS_ORGHIERARCHY ")

6. Delete the CDT
7. Re-upload the updated CDT
8. Run impact analysis to update your data store (assuming the Data store is inside an application)
9. Update the data store

That has to do with the way the library used for query rules work. Here's what you need to do:

APPROACH #1:

1. Change the schema name that owns this view to be lowercase.
2. Edit your XSD to use the schema="" attribute and put the schema name in lower case

@Table(name="" schema="")

3. Delete the CDT
4. Re-upload the updated CDT
5. Run impact analysis to update your data store (assuming the Data store is inside an application)
6. Update the data store

APPROACH #2

If you cannot rename it to lowercase (which is the default behavior of Appian for DS validation) then you will have to do this:

In DB2:

1. Login as the SCHEMA who owns the view
2. Grant privileges over the VIEW to the Appian ID
3. Login as the Appian ID
4. Create a synonym where XXXXX is the Schema that owns the view


CREATE SYNONYM UPS_ORGHIERARCHY FOR XXXXX.UPS_ORGHIERARCHY;

5. Make sure your XSD has the following annotation WITHOUT ANYT SCHEMA NAME

@Table(name="UPS_ORGHIERARCHY ")

6. Delete the CDT
7. Re-upload the updated CDT
8. Run impact analysis to update your data store (assuming the Data store is inside an application)
9. Update the data store