Create Record Action saves to database but does not appear in grid until a Data Sync is done

Question

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?

insurityapp0001 · Accepted Answer

After additional trial and error, I was able to figure this out myself. I will explain the solution here in case anyone else has a similar situation. 
 The database table I created was using a guid for the primary key. When I initially established the Create Record Action it was failing because of missing not nullable data. Since I couldn't figure out how to generate a guid in Appian, I allowed the column to be nillable on insert from Appian by editing the XSD for the data type and then I added a database trigger to set the key value on insert. After creating a new Data Type that used an integer for the primary key and testing the Create Record Action it worked and it finally dawned on me that the record was not returned to the grid after insert because Appian didn't know the key value for the record that was inserted. 
 To fix the problem, I created an expression rule to generate a guid, then modified the Process Model to use a Script Task that sets the key value using the expression prior to the Write new Code to DSW call and removed the trigger code to prevent overwriting of the key value sent by Appian. Now that the key value is established in Appian, it can return the record that was inserted immediately after save. Problem is now resolved.

virat yogi · Answer

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.

virat yogi · Answer

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"

Mike Schmitt · Answer

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.

Mike Schmitt · Answer

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.

GopalK · Answer

"immediate sync" happens as soon as you update , add or delete the record.You dont need to re-sync the record. You can just refresh the record using refresh button like below snap, 
 
 There is also a functionality where you can configure refresh interval . 
 
 Though i am unsure about auto refresh after any record action.

Create Record Action saves to database but does not appear in grid until a Data Sync is done

Top Replies