- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2024 11:58 PM
Hello,
I have a question about a report, that shows a numerical value behind Label. This is disturbing to users and we'd like to remove it.
Here, its because the report uses a database view, using the im_idea_core table, as parent value. However, for this table, the value for completed is 2, and the conflicting value comes from a different Teamspace - that the report is not even using!
Is there any way how to hide the value, other then changing the underlying data in the whole instance?
Thanks
Best regards
Pavel
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2024 01:34 AM
The problem is that 'state' is not evaluated on the string value, but on the technical value. You have two 'completed' states with the same value, hence it's showing like that. You can try to exclude the records you don't need, but since it's a DB view I am not sure if you can. It will need to be through the conditions on the report, because you can't hide that value. It's just their because you are checking on the state from different tables with the same value which is all inherited.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2024 01:34 AM
The problem is that 'state' is not evaluated on the string value, but on the technical value. You have two 'completed' states with the same value, hence it's showing like that. You can try to exclude the records you don't need, but since it's a DB view I am not sure if you can. It will need to be through the conditions on the report, because you can't hide that value. It's just their because you are checking on the state from different tables with the same value which is all inherited.
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2024 03:38 AM
Yes, thank you - ended up switching the table in DB view for one lower in the dependency tree, after that still didn't work, I changed the field used in report for one matching the table and then it worked.