I tried to do an argument to hide the linked reports if there weren't any values but they are still showing on my project profile. Is there a way to hide a table report embedded in a project profile if there are no records in it?
I have already tried the following argument with no luck:
If <linked field> = to blank then hide <linked field>
------------------------------
Teresa Ray
------------------------------
Question
Hiding a Linked Report Field when there are no values
This topic has been closed for replies.
+12Teresa,
What you need is a summary field that will tell you if there are any child-records in that table. If it is a directly-connected table; then you simply build a summary field to count the number of records; and write your rule from that. If the records are held in another table further down, but not directly connected; you will need to pass them "up" through the relationships so you can use it to write your rule.
Think, however, also that if you do not see the embedded report, you have no visual confirmation that there are /are not records. Having the embedded report show "no records found" confirms that there are no connected records.
While I support the "clean" look of a form that does not show all the embedded reports when there are no child records; I usually recommend at the very least displaying the [Total # of Child Records] fields so there is still a visual-confirmation of the existence or not of records.
It is easy to assume that not seeing a section/embedded report means that there are no records; whereas other users might know there should be some and something has gone wrong (orphaned records).
Consider both sides of the argument to see or not to see the information.
------------------------------
Laura Thacker (IDS)
laura@intelligentdbs.com
(626) 771 0454
------------------------------
What you need is a summary field that will tell you if there are any child-records in that table. If it is a directly-connected table; then you simply build a summary field to count the number of records; and write your rule from that. If the records are held in another table further down, but not directly connected; you will need to pass them "up" through the relationships so you can use it to write your rule.
Think, however, also that if you do not see the embedded report, you have no visual confirmation that there are /are not records. Having the embedded report show "no records found" confirms that there are no connected records.
While I support the "clean" look of a form that does not show all the embedded reports when there are no child records; I usually recommend at the very least displaying the [Total # of Child Records] fields so there is still a visual-confirmation of the existence or not of records.
It is easy to assume that not seeing a section/embedded report means that there are no records; whereas other users might know there should be some and something has gone wrong (orphaned records).
Consider both sides of the argument to see or not to see the information.
------------------------------
Laura Thacker (IDS)
laura@intelligentdbs.com
(626) 771 0454
------------------------------
Sign up
Already have an account? Login
Login to the community
Login with Quickbase US – quickbase.com Login with Quickbase EU – quickbase.eu
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.