Hello everyone,
I have a table with several fields 'year_field' and 'month_field' forming the table's primmary key. It's mandatory that the fields remain as primary key. When I do that, Appian doesn't allow you create record or cdt associated with the data store.
I have come up with a solution, but it might not be the optimal one. I will show it to you just in case either you have something to add or different way to make it better.
The idea is to create a procedure to write, update and delete data in the table. Instead of using 'Write Record' node, the procedure would be triggered based on the operation you want to perform.
For reading purposes, I have thought to create a 'Materialize View' where the view includes the primary key.
That is my solution. If you have a smarter way to do this, please let me know.
King regards and thanks
Discussion posts and replies are publicly visible
Why not just use the autogenerated primary key? You could procedurally generate values for an arbitrary number of other fields to serve as informative metadata, sorting-order columns, or many other things, without requiring those to be "the primary key", and honestly it sounds like you're bending over backwards to invent a solution to something that was not a problem in the first place.
I can not. The table is related in several app out of appian and the client demands no changes in the table. Even we try to change it and the result was an error in somewhere. In conclusion, the table can not be altered.
Then it sounds like client's demands are keeping you from using RecordType data - you'll probably need to stick with a CDT approach until something changes.