How to refresh dynamically a RecordType inside in an interface?

Question

Hi, 
 Could you tell me how a filtered RecordType grid (placed inside an interface) can be refreshed please ? 
 My RecordType data are retrieved from the a!recordData() function, and is filtered on the field "deleted" (all rows are visible if delete = "false"). 
 I have a button that calls an Expression Rule to update the underlying table to set the "deleted" field of the selected row to "true". 
 (I use the WriteToDataStoreEntity Smartservice). 
 After the table is updated in database, I have click to click on the "refresh" icon of the RecordType to see that all is working fine : the lines are hidded. 
 How would you refresh the RecordType, without a manual user action please ? 
 
 (I intentionnaly do not use any process model for this example)

Peter Lewis · Answer

I think what Danny is saying is that there is a parameter directly on the grid that allows you to refresh based on a referenced variable change - in cases where a!recordData() is used, you can utilize these parameters on the grid to provide the same behavior as you would get from a!refreshVariable(). 
 For instance, I think if you try adding this line within your grid it should work: 
 refreshOnVarChange: {ri!selectedvehicle.deleted}

Mike Schmitt · Answer

Ok, I've been able to confirm your reported behavior by setting up a small sample interface that does basically the same thing you're doing. I'm afraid this *might* be expected behavior of a!recordData() , given that there's a built-in refresh button on the interface that might be intended to be the *only* refresh functionality for the data. 
 Hhowever I agree that it does seem unintuitive that this data won't refresh as part of a refreshVariable, especially when we want to do it intentionally. You might want to open a case with Appian Support, reporting this as a possible bug, and at least an oversight in actual behavior versus expected behavior for designers. 
 Edit: to confirm, I also created a random dynamic link to increment the refresh counter in my example, and did it 20 - 30 seconds after the (successful) DB write was completed, and it still doesn't cause the loaded data to refresh. If this is the "official" behavior, it's certainly surprising and unintuitive. 
 Edit 2: per the documentation , it appears as if it might not really be supported functionality to store queried recordData in a local variable (even though fortunately it does seem to work); this would imply to me that it's not subject to the refresh conditions as defined in a!refreshVariable() .

Mike Schmitt · Answer

The only other way I'm used to is to build your own record filtering (which isn't very hard) and populate the grid using data pulled straight from a!queryEntity(). You give up some of the OOB "record list" functionality and gain more flexibility, including, i expect, the ability to have the grid automatically refresh after your deactivation has been fired.

ManuelHTG · Answer

the best solution I can think is to use a local variable that refreshes

Mike Schmitt · Answer

Sorry for the late reply cedric01 - Community doesn't see fit to notify me that you've replied to me for some reason. Anyway. I usually use a special local variable to update at the end of a data change (by utilizing the onSuccess parameter of the WTDS rule), which then causes subsequent variable values to be refreshed. This can slot straight into your code -- I haven't used a!recordData as much, so I'm making a little bit of an assumption that it'll work the same way here. 
 /* make the following changes to your form local variables: */
 local!refreshCounter: 0,
 local!data: a!refreshVariable(
 value: a!recordData(
 recordType: 'recordType!vehicles',
 filters: a!queryLogicalExpression(
 operator: "AND",
 filters: {
 a!queryFilter(
 field: 'recordType!vehicles.fields.deleted',
 operator: "=",
 value: false
 ),
 },
 ignoreFiltersWithEmptyValues: true
 )
 ),
 refreshOnReferencedVarChange: true,
 refreshOnVarChange: {
 /* ri!selectedvehicle.deleted */
 local!refreshCounter
 }
 ),

/* then one small change to your helper rule call (or, if it's used in other places and you don't want to risk new changes, just perform the WTDS action here until you can tell whether it'll work for you) */
a!buttonArrayLayout(
 buttons: {
 a!buttonWidget(
 label: "",
 icon: "arrow-right",
 saveInto: {
 a!save(ri!selectedvehicle.deleted, true),
 rule!VH_SaveVehicle(
 selectedVehicle: ri!selectedvehicle,
 refreshCounter: local!refreshCounter /* Added */
 )
 }
 )
 },
)

/* Then the change within the helper rule itself */
a!writeToDataStoreEntity(
 dataStoreEntity: cons!VH_ENTITY_VEHICLE,
 valueToStore: ri!selectedvehicle,
 onSuccess: {
 a!save(
 ri!refreshCounter, /* integer */
 ri!refreshCounter + 1
 )
 }
),

Mike Schmitt · Answer

cedric01 that might be it, but just in case, could you post a current representative sample of your code? What happens if you try basically the same setup but using data you get from a queryEntity rule?

How to refresh dynamically a RecordType inside in an interface?

Top Replies