Orchestra Plugin - Removed Items from Repeating Group still trigger

Need help Plugins
1

I am using the Orchestra plugin inside a repeating group.

Say I have 10 standard shopping items. This week, I decide I only need eight items from the list.

I remove the two items from the repeating group. When I click the action to trigger the musicians, the ten items still get pushed through.

If you inspect the elements, you can see the removed line items are still there but invisible.

Musicians
Musicians1546Ă—300 30.7 KB

I tried resetting the repeating group, resetting inputs, and reinitializing musicians, but to no avail. The only way to clear it is to refresh the page.

Any ideas? @ZeroqodeSupport

2

Hey Jeff :slight_smile:

Have you tried adding a condition to the musicians workflow so it only runs if “this musician is visible”?

I’m also curious how you’re updating the RG data source when you remove the items and what kind of resetting you’re doing every time you click the action to trigger. It’s possible you may have conflicts from previous runs before you removed items?

1 Like
3

You got it. I missed that one.

I added the “this musician is visible”? condition and it worked.

Thanks Gaby…

I am pulling the RG data from a State. When I remove the data, it updates the state.

2 Likes
4

Just came across this and will be trying the same - thanks for the suggestion.

I actually submitted this a possible bug to Zeroqode last night but have yet to hear back.

I am using the Orchestra plugin to do this in a Table element and it does not appear that the indexes refresh when the data source changes.

For instance, I have a table of items with a data source that includes a search constraint equal to a user dropdown. If I change the dropdown to a new user, the table updates, but when I trigger the musicians, it is running and calculating off the old position of data/rows. This is especially problematic if the table contains more or less rows between the two users.

I have tried everything to get the data to refresh including using states to hide/unhide the musicians, the tables themselves, and so on, but was not successful. My next step is to try to fork the plugin code and write a refresh piece if needed.

5

It does appear this is working for me as well in brief testing. I had tried to attach this to the step inside the workflow (which is not an option) vs. the workflow itself. I’m guessing there’s some caching going on here as stated by the OP where it’s hidden vs. actually gone/refreshed.

1 Like
6

I did hear back from Zeroqode support that this issue could be due to them not fully certifying the plugin for use with table elements. I informed them of this thread and how this was definitely an RG problem as well.

They suggested another likely workaround of clearing the data source and then adding it back after a brief delay as a way to reinitialize all musicians.