I just updated a data type (added fields to it) and all related objects were upd

judym598

Certified Senior Developer

over 9 years ago

I just updated a data type (added fields to it) and all related objects were updated successfully (or so it said). The Data Store looks fine, process model is fine and the interface rules that use this data type work just fine but I have 2 query rules that are not longer working. I think they are trying to use the old data type. I've reselected it for the query but it still doesn't work. I even deleted the query and recreated it but it's still not working. Any suggestions on why that would happen? This is the error I'm getting. The data type is IPS_Board.
Expression evaluation error in rule 'ips_getallboardschedules' at function 'queryruleexec': Error evaluating function 'queryruleexec' : Unexpected error executing query (type: [IPSBoardDT2578], query: [ips_getAllBoardSchedules], order by: [[Sort[id asc]]], filters:[null])

Discussion posts and replies are publicly visible

0 patrickh over 9 years ago

What fields did you add to the CDT? What are their types and what are the types of the corresponding columns in the database?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 judym598
Certified Senior Developer
over 9 years ago

I added 3 date fields - same as in the table. Everything else is working except my 2 queries. I checked for outdated dependents and there are none. No issues in the process model where this data type is used (i.e., IPS_Board^4...or something like that). I thought deleting the query and recreating it would work but it didn't.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 judym598
Certified Senior Developer
over 9 years ago

I didn't want to have to drop the data type altogether or drop it from the data store and re-add it because I know I'll definitely have to reconnect all the objects that use it but I can't think of any other option. I've added fields to other data types in the past and didn't run into this problem.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 patrickh over 9 years ago

What did you set as the default values for these new columns in the database? Query Rules can fail like this when you try to query a database table with date fields that have *no* value. That is, "No Value" has been selected as the default value for the new date columns. This is different from a default value of NULL, which Appian can handle. Try inserting NULL as the value for these new columns in each existing row.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 judym598
Certified Senior Developer
over 9 years ago

You were right about the date fields. I updated the default value from 'none' to 'Null' and then reverified the data store/republished it but I'm still getting the same error.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Chris over 9 years ago

I've had issues with re-mapping data stores sometimes, in these cases I would try to update the DS again by re-selecting the CDT within the DS entity. Also make sure you remove the CDT from the line in the selection box before re-selecting, then verify, save/publish.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 patrickh over 9 years ago

Updating the default value is one thing, but did you actually insert NULL as the value for these columns for all existing rows? Updating the default won't do this to the best of my knowledge. What RDBMS are you working with?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 judym598
Certified Senior Developer
over 9 years ago

That worked! I went into the table (MySQL) and set the new dates for all records to 'null' and now the queries are working. Thank you!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel