I simply try to let User choose from records in same namespace but different module and work on that record.
I hope its not too stupid to ask, but i couldnt find the answer, tried couple of things.
First i added a Function with Type “Compose records search” and piped the result in the “options” Field on the options Prompt which obviously didnt worked.
Now i created a empty KV with name “begleiter_list” and then an iterator which goes through the desired records and hits an expression like f.e.:
I also tried a few other approaches i didnt recall. i really hope you can give me a hint here.
Most of the time i get error:
workflow 272618223415853060 step 15 execution failed: expression “set(begleiter_list,begleiter.values.generatedname, begleiter.recordID)” failed: expected type expr.merger for parameter 0 but got map[string]string
What version are you using? I quickly threw together an example and it worked as expected (I’m running the 2022.3 dev version but this bit should be the same for 2021.9 also).
You can find the exported workflow on this gist.
A few things to note:
KV only allows string values for both key and value, so your first bullet won’t work since recordID is an uint64 under the hood.
my example uses format to get the recordID from uint64 to string.
Lastly, we’ll be adding a native support for a record picker (probably in 2022.3), but in the meantime, this workaround would do the trick.
Hi tjerman,
Thank you for the workflow, but i didnt got it to work, im on version 2021.9.6
I keep getting error:
workflow 268272284018409474 step 10 execution failed: expression “set(test, format(”%d", record.recordID), record.values.name)" failed: expected type expr.merger for parameter 0 but got map[string]string
I tried your workflow with just the change in module and namespace at iterator obj.
Can you think of a different workaround? Maybe using a different datatype (Not KV)?
Oh, i didnt realised .7 is already out. I just upgraded but sadly i still get the same error.
Also deleted all website data along with cookies and cache just to be on the safe side
That’s strange… I’ll do some debugging to see if I can figure it out.
Just to be on the safe side; if you go to the /version route (example https://latest.cortezaproject.org/version), make sure you see the .7 patch.