Skip to main content
nmillesonAnswer
Feb 22, 2021 1:38 PM UTC

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.

4 replies

Feb 22, 2021 11:04 AM UTC

Try using MashupPropertyBinding, and have the key as the infotable name, and the value as the mashup parameter in the row mashup.

 

 

Feb 22, 2021 11:23 AM UTC

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.

nmillesonAnswer
Feb 22, 2021 1:38 PM UTC

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.

Mar 2, 2021 4:17 PM UTC

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