Hello, I have problem to use Filter in data inspector. I have opened shapefile in inspector and i wanna filter some feature, but filter possibility to choose filter according to attributes is frozen. Please check picture below.
Thank You for tips!
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
That's really odd, it looks like you're running data to an Inspector (and running with full inspection at the same time). In both cases you should be able to pick an attribute.
Is it only happening with this dataset or also with others?
That's really odd, it looks like you're running data to an Inspector (and running with full inspection at the same time). In both cases you should be able to pick an attribute.
Is it only happening with this dataset or also with others?
Unfortunately, its happening everytime when I try to open dataset of all kind... Even when I export data from workspace to inspector (via redirection to inspector) or when I only start inspector alone...
What version are you using? as I noticed this in the initial 2016.0 release. I didn't have an issue with 2016.1 or possibly even a later release of 2016.0. I have uninstalled now so can't check the build numbers
Unfortunately, its happening everytime when I try to open dataset of all kind... Even when I export data from workspace to inspector (via redirection to inspector) or when I only start inspector alone...
Okay, in that case I agree with @ciarab: try to upgrade to the latest 2016.1 build if you haven't done so already and see if the problem persists. If it does I think you're best off contacting either Safe support or your local reseller.
What version are you using? as I noticed this in the initial 2016.0 release. I didn't have an issue with 2016.1 or possibly even a later release of 2016.0. I have uninstalled now so can't check the build numbers
What version are you using? as I noticed this in the initial 2016.0 release. I didn't have an issue with 2016.1 or possibly even a later release of 2016.0. I have uninstalled now so can't check the build numbers
Yes, sadly this was broken in the first release of 2016. It was fixed very quickly though, so you should be able to upgrade to any build 16171 or greater and find it works OK. Apologies for the inconvenience this is causing.