I have created a simple table in the same database as aavehicle and I created a data model for the table along with CREATE and UPDATE record actions. When I add a new record using the CREATE record action and associated UI, the data does not appear in the record List until after I run a Data Sync. When I UPDATE a record using the UPDATE record action and associated UI, the changes are reflected immediately in the record List. I have scrolled through all pages of the list and confirmed the new record does not appear. If I query the database BEFORE running the Data Sync, the new record is in the database. Any ideas why this may be happening?
Discussion posts and replies are publicly visible
Hi charletonh0001
If the data sync is enabled, any CRUD operation using the related actions of the record will trigger the sync and data will be updated. Sometimes it fails which you can see in the sync history.
Can you try to update/ create something using the related action of the record and have a look at the sync history, If it will fail you will see the status in the data sync tab under sync history.
Hi! Thanks for your response. After adding the new record through the Create record action, there is no new sync history row. If I click the START SYNC button, the new record is returned from the database and a new row is added to the Sync History. I expected the sync to happen immediately once I clicked the submit button when added a new record, but it is not. It does immediately sync when I use the Update record action, but not Create. When I add a new record, the only way I can get the new record into the grid is to perform a manual sync.
Can you check it in the Records Tab of Tempo, whether the new record is coming up there after you create it? If it appears in the Tempo, in the grid try to set the "refreshAfter" in the grid to "RECORD_ACTION"
refreshAfter:"RECORD_ACTION"
Also, make sure your process chains through the 'Write to data store node' so that Appian writes your value to the database before the page reloads
I checked the Record Tab of Tempo and the record did not appear there after creating it. I haven't been able to find the refreshAfter option anywhere, but I will keep looking and if I can find it, try your suggestion. Thanks for your response.
Thank you. The record is written to the database. The process model is a simple auto-generated model so I can't find anything to change there. I will keep looking.
insurityapp0001 said: The process model is a simple auto-generated model so I can't find anything to change there.
Are you saying you confirmed that Activity Chaining is enabled all the way through to the WTDS node, as Danny said? You may need to do this manually in your process model, and it definitely does affect the behavior you're experiencing.
No, I didn't say anything about Activity Chaining. I am new to Appian and I don't even know what you are referring to with Activity Changing. I was just trying to create a simple example that will create and update a record in a database. I used the Generate A Record Action automation to establish the Create and Update actions and didn't change anything in the underlying process models. I assumed that the auto generated actions wouldn't require me to change the process models to get the Create Record to work properly since the Update Record does work properly. As I indicated earlier, I will keep looking. Thanks for your response.
I'm unsure what the auto-generated process model will or won't have, so I can't speak to that either way. I was merely trying to clarify what Peter was trying to point out - specifically, that "Enable Activity Chaining" needs to be enabled on each activity flow line up until the WTDS node.
Without this, the functionality will still work, but it is known to often exhibit the behavior you're describing and trying to remedy here, which is why we're asking you to confirm this.
Ah! A picture is worth a thousand words. Thank you for providing. I checked the process models and for the Create Record Action I see the chain:
For the Update Record Action I see the chain as well:
Thanks for confirming, the current configurations we can see here are enough to confirm that this piece isn't affecting the behavior you're seeing, as far as I know.