Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We have a very strange situation where there are fields that are showing up in edit mode (when creating master items or when adding dimensions/measures to a viz object) - but the fields do not show up in the Selections tool (even after checking the "Show fields" box. We're wondering if this is some kind of bug?
The fields have not been tagged as hidden, and they function and display like normal in every other situation - except for the Selections tool. Master items have not been created for these fields yet - they've initially only been offered to users as fields for now. (Yes, we will be creating master items eventually - and they do work as they should when they're included as master items - they just don't work correctly as fields.)
I'm adding some screen shots for one of the fields below, to show what we're seeing. Any help anyone can give us on this would be appreciated. Thanks!
It would probably take too much time to strip down one of our apps to the point where I'd be allowed to share it externally. But to answer a few questions, this behavior only happens with a small group of related fields (all of them are pharmacy fields). We have hundreds of fields in our apps, and as far as I know all of them work but this group of 6 fields.
Our working theory right now is this: to do our field aliasing, we pull from a table in SQL. We're thinking that there may have been invalid characters (carriage returns, etc.) in the field names of these pharmacy fields in SQL, and that caused the fields to become corrupted somehow. They work in every other way, they just don't show up in the Selections tool. We've checked the SQL table now and there are no invalid characters now, but we thought there might have been some initially, and that caused all our apps to be corrupted for those particular fields.
One interesting thing: I binary loaded this app into a brand new app to see what happened - and that fixed the issue. All the pharmacy fields showed up in the Selections tool. This is part of the reason why we're thinking there may be some corruption in the original apps. But since the field labels are correct in SQL now, loading data to brand new apps works.
One other thing: I did look at the F12 console, and there were two 404 errors:
-Cannot GET /api/v1/accesscontrol/evaluation
-The requested resource cannot be found.
And one other error: #1: singleSpa.start() was not called
I have no idea if any of these errors have anything to do with this issue or not.
