I have a repeating group (RG1) that gets populated from an API call to an external database. When the user clicks on a row on the RG, it populates another RG (RG2) from another API call to the external database. If the users selects another row in RG1, it repopulates RG2 correctly. However, if they click back onto the same record they previously selected on RG1, it shows no records in RG2 (even though they do exist). If you then refresh the browser, the records now show in RG2. Any ideas on how to make RG2 refresh correctly when switching records in RG1? Both RG’s API calls pass a unix timestamp extract (to be sure the API call is slightly different, so it forces a call vs caching. Puzzling.
This topic was automatically closed after 70 days. New replies are no longer allowed.