I've got a system in place that allows for the creation of X number of child records, where the records automatically assign themselves their count in the list.
So if I create a set of records through a sequential action loop, the records are created with the numbers:
It seems that this has just broken for me.
Now everything returns the final count + 1:
________________________________________________
I'm wondering if anyone else is seeing this as well?
((UPDATE))
I didn't have anything that demonstrated this functionality aside from the app I'm currently working on, so I couldn't go elsewhere and test.
So there must be something off with my setup... I'll have to dig deep to debug this one. (^_^)
It seems like, in my system (for whatever reason), when the loop runs - the records aren't saved immediately or something. Like the numbers are in limbo until the final thing we're doing is done, then the formula's finalize and set their numbers - but by this point the count has changed.
https://share.zight.com/llu8oWOA
There is definitely something funky happening. I'm gonna submit a help request.
Yes, I have had an issue like that. Test the app in your smartphone (I guess you won't have the same problem) or if you set the desktop mode to the older version I guess the problem will be solved as well.
In my case it seemed that the app wasn't fast enough to run the calculation and I simplified the formula, it worked and then problems again.
Now it is working fine. I don't know if the server was having some slowliness problems.
@MultiTech wrote:
There is definitely something funky happening. I'm gonna submit a help request.
@MultiTech I see[Related Chain_Links] is a VC ? If so create a duplicate PHYSICAL column with same expression used in [Related Chain_Links] and I would call it [Related Chain_Links Physical] with ENUMLIST type column and retry by replacing same Physical column in below expression.
I have been facing same issue for a while and replacing VC with Physical column had helped me. I have a ticket open and they were not able to find the root cause. So I left following up.
Also, try using the action in order to add the sequential number instead of the Initial Value config.
Just for testing
@SkrOYC wrote:
Also, try using the action in order to add the sequential number instead of the Initial Value config.
@SkrOYC In cases where you need to reference the parent of a target table, this approach might not always be effective. It's particularly challenging to make such calls from the source table where looping begins. There was a known issue or uncertainty regarding this, specifically about initial values not functioning in looping actions. This was notably apparent with the release of the desktop UI. However, it's believed that this issue was resolved a few months ago.
User | Count |
---|---|
36 | |
8 | |
3 | |
2 | |
2 |