Passing infotable parameter from child mashup to parent

[MA8731174]

Hi,

In a child mashup I have a grid with rows. I exposed a grid parameter (selectedRows) and bound it to the mashup parameter which is also of infotable. But when I try to use this parameter in the parent mashup, I don’t get any data.

Instead, I see developers usually create expressions then bound that mashup parameter of infotables singe value like field in it... to extract single values (like Id, State) and pass those to the parent.

 Is this the expected behavior?

• Why can’t the parent directly consume the InfoTable parameter?

• Is there a clean way to expose the whole SelectedRows to the parent, or is best practice to always send only the needed values?

Thanks!

my expression which i bind from my mashup parameter(infotable type and use that single field to bind with input parameter of this expression ) to get the value and then bind the output again to the mashup parameter which is of string type to get that value in parent mashup....

[TonyZhang]

Hi @MA8731174,

I tried your senario in TWX 9.6 and it worked fine.  There was a bug that has been fixed, can you check which ThingWorx version you are on?

https://www.ptc.com/en/support/article/CS417737

https://support.ptc.com/help/thingworx/platform/r9/en/index.html#page/ThingWorx/Help/Release_Notes/FixedIssues/Fixed_Issues_in_ThingWorx_Platform_9_4_4.html

"Fixed an issue where connecting Infotable Mashup parameters to a widget didn’t work properly"

Best,

[MA8731174 · Accepted solution]

We are using Thingworx 9.3 version and In ThingWorx 9.3 and 9.4, you can solve this issue by creating an expression to extract a single field (e.g., Id, State) from an  infotable which itself is a mashup paramter of type infotable and has binding with selectedRows of that grid widget to get one selected row and then bind that value with an expression and get the output and bind to another  mashup parameter of type STRING which can then be accessd in parent mashup. This workaround works fine for passing values up.

However, as @TonyZhang already mentioned in the thread, this issue has been fixed in all later versions of ThingWorx. On those versions, you can directly expose and bind the full SelectedRows infotable parameter from the child mashup to the parent mashup without needing expressions.

[TonyZhang]

Hi @MA8731174,

If you think you have received the solution to your question.  For the benefit of other Community Members who may have the same question, it would be great if you could designate it as the Accepted Solution.

Thanks for using the PTC Community!

Regards,