Community Tip - New to the community? Learn how to post a question and get help from PTC and industry experts! X
I've had the same issue in 9.0 and it's a known issue (TW-80435). To get around it, you can convert your infotable to JSON before passing it to your collection widget, and then in your collection mashup(s), just convert it back to infotable from JSON. It's a bit of a pain but it was the only way for me to get it to work.
Try using MashupPropertyBinding, and have the key as the infotable name, and the value as the mashup parameter in the row mashup.
Is it possible to add it to as a global parameter this infotable?
Because have other data assigned to the mashuppropertybinding that I don't constantly want to reload
by adding this extra infotable.
I've had the same issue in 9.0 and it's a known issue (TW-80435). To get around it, you can convert your infotable to JSON before passing it to your collection widget, and then in your collection mashup(s), just convert it back to infotable from JSON. It's a bit of a pain but it was the only way for me to get it to work.
Hi @TS_9588135
If you feel your question has been answered, please mark the appropriate response as the Accepted Solution for the benefit of others with the same question.
Regards.
--Sharon