For the good of the community, I experienced an issue regarding Perspective Custom properties for a project. This issue was experienced with Ignition version 8.1.26, but I can't say it would be isolated to just this version.
ISSUE:
I noticed a session of my Perspective project throwing errors on a View and noticed objects bound to session custom properties were not showing values.
After some digging, my custom properties were gone. I tried adding them back in, saving the project and closing and reopening the project again in a fresh Designer instance, but with no luck. The properties were gone again.
I noticed that other projects on the same gateway still had their custom properties when opening the projects in the Designer.
This led me to believe that there may have been some sort of corruption or 'disconnect' somewhere with just this one project. With this thinking in mind, the following remedy worked to resolve this.
REMEDY:
I had a fresh export of the project. I deleted the project from the gateway and did a fresh import.
I added one custom property and saved it just to test. It worked.
I added the rest of the properties and saved the project and it is running as expected again.
I just had the same issue. I’m working on some charts in Perspective, they had a custom property as well as a dataSource object binded on their custom prop, but I don’t see them anymore and restarting my designer doesn’t change anything. What’s weird is that I can still see the blue color next to dataSources as if there is still a dataSource with a binding:
yes but the small blue bar indicates that there is a binding on one of the prop in the object, right? but in this case there is no prop under dataSources, but still Ignition believes that the prop with the binding is still there in a way
Yes, I see. Bindings that are attached to inner elements of lists or objects aren't deleted when their target is deleted. You may need to examine the view's JSON (shift-right-click in the designer tree) to locate the named target. Add it back so you can see it to remove it. (Or carefully remove it from the JSON.)