Refresh Summary View

Question

Hi, 
 I have some refresh problems with a Summary View. The View is composed of a dashboard (Record Type A) and a read-only grid (Record Type B). In the dashboard, there is a Customer Record Field (field C) aggregating Record Type B. When I try to add a new record in the grid, the grid updates itself (so chaining should be ok), but field C doesn't unless I force manually the updating. Any suggestions?

Mike Schmitt · Answer

I'm not sure, but by any chance, have you tried adding a "Sync Records" node pointing to Type B within the chaining after the new entry is added?

Mike Schmitt · Answer

katafina1470 said: removed the cast from the query, but field C doesn't refresh. It is as if the refresh input doesn't propagate from Record Type B to A. 
 I feel like we haven't narrowed down the exact problem yet. Is the issue that the RECORDTYPE has not SYNCED? Or is the problem only that the ON-FORM local variable is stale afterwards? 
 For instance, if you reproduce this issue on an interface, but then open a separate query rule and QUERY the data, does it show the correct value even while the interface doesn't? This is a crucial thing to know here because until this is narrowed down, all these suggestions are mere guesses. FWIW this is troubleshooting 101 and is something you should probably be doing ahead of time, though we're happy to step you through it if you're not used to it yet.

Mike Schmitt · Answer

Ok, thanks - then this seems like it's most likely a standard "on-form variable refresh" issue (though maybe it's enhanced in this case by something that's happening extra-slowly in the back end that we have no direct control over, though if so, i'm not sure what). 
 Can you post a screenshot of your process model, including the nodes that create all new data?

Mike Schmitt · Answer

If you already tried adding a "sync records" node following your "write records" call, pointing to the identifiers of the written records for your type, and that didn't help with your issue - then I assume there might just be an issue where the calculated value is being resolved in the back-end too slowly to be reflected right away on your interface. Maybe you can seek specific feedback from Appian on this, IMHO it may warrant a support case.