I use an embedded view as a widget in my project. I create a folder that contains the tags for the view. All the view parameters are indirectly bound to objects in the embedded view based on a single parameter “Path.” I configure an event script on the main page to update the “Path” parameter when a user selects an object.
The event script updates the “Path” parameter to load values from another folder.
It works, but makes modifications time consuming. I reorganized my tags in a UDT and modified the view to bind to an instance of the UDT, however, I can no longer bind the view to an instance of the UDT by scripting.
If you’re passing the instance path as parameter, you could make a custom prop that binds to the instance directly using that path.
What is your script doing ? Is the one you mentioned that changes the path when a user selected something ?
I have multiple transmitter graphics on a page. When a user clicks on a particular transmitter, the script modifies the “Path” parameter of an embedded view that contains more detailed information about the transmitter. All other parameters of the embedded view are indirectly bound with the Path being the variable that selects the transmitter information to be displayed on the embedded view app. The embedded view with indirectly bound parameters works, but it’s not as clean as directly binding to a UDT instance.
The original way I set up the embedded view uses indirect mapping. The Path parameter is the variable part and the rest of the parameters use Path to indirectly bind to other tags. That setup works fine. I’m looking for the correct script syntax to bind a UDT instance to an embedded view. My guess is that the UDT is se tup like an object whereas the Path parameter is a single value.
