Issue with indirect tag bindings in ignition perspective

[srinivasan_s]

I have issue with indirect bindings. I have three process and each process has three machines. Attached the tag lists.

I have also attached the main screen.

In that screen, firstly I will select the respective process and respective machine. Based on that selection, tag value which is binded with text property should change.

What I have tired,

I have taken the dropdown values which is process and machine number over message handler, need to just change the value according to that selection which is path,

tag path will be like - "[default]Mixing/M001/m_body_temp1"

bit long question, kindly some one help me out. Stuck for a long

[bschroeder]

You have an expression transform but nothing in there...

Also if you hover over the Tag error on the bottom, what does it say? that will give you and idea of what is going on.

[srinivasan_s]

Thank you for your reply. That's where I am stuck. Don't know what to use in expression transform. Kindly help me ! to map the tag path accordingly.
error : Expression transform is empty.

[bschroeder]

First remove the expression binding.

Then I need to see the error that is being generated by:

You are referencing

{view.custom.process}

and

{view.custom.machine}

Do you know if those have valid values?

[srinivasan_s]

Yes i have removed it.

Error:BAd_not_Found.
Note: {view.custom.process},{view.custom.machine} this custom variable will get the value over message handler, in view A to View B which is embedded view in View A.

[bschroeder]

@srinivasan_s

Error:BAd_not_Found.

If you hover your mouse over the error you should get more information that might help.

The tag you are creating with the references of {view.custom.process} and {view.custom.machine} isn't creating a tag path that exists.

Can you post the actual values, or a screen shot of your custom props showing those values?

[rbabcock]

You should rename those tags in the subfolders so they're all the same. The problem you're running into is you're building the tag path:
"Grinding/G003/m_body_temp1"
which does not exist.

[srinivasan_s]

Thank you all for your reply. Will check and get back to you
@bschroeder @rbabcock

[pturmel]

@rbabcock

should rename those tags

Concur. Remove the letter prefix and numeric suffix from all of those innermost tag names. Then your parameterized views can accept a simple tagpath parameter that contains [someProvider]Grinding/G003 and your indirect binding would be just {1}/body_temp.

[srinivasan_s]

Thank you. I have corrected.

Thank you all @bschroeder @rbabcock for your immediate support.