Gilbert13

Hide object based on value in portal row

7 posts in this topic

Hi,

I am trying to hide object (Parent::Temp 4) if the field in the initial portal row 4 is empty.

IsEmpty ( Child::Text ) I don't know how to specify the portal row in the calculation, Please help...

Thanks

 

Temp.fmp12

Share this post


Link to post
Share on other sites

Maybe this file from John Mark Osborne Hide Row will help.

Here is another file that may help Raybaudi

Share this post


Link to post
Share on other sites

Posted (edited)

4 hours ago, Gilbert13 said:

if the field in the initial portal row 4

What exactly does "initial portal row 4" mean? I think "initial" means "first" - so what is the meaning of "4" here?

 

4 hours ago, Gilbert13 said:

 I don't know how to specify the portal row in the calculation

You probably want to use the GetNthRecord() function. Note that this counts the records by their order in the relationship, not in the portal. If your portal is filtered and/or sorted in a different order, then there will be a difference.

 

I must add that your question raises some red flags regarding your structure. Why do you need numbered fields in the parent table? It seems you are trying to mirror the child data within the parent record, thus defeating the very purpose of having a related child table at all.

 

Edited by comment

Share this post


Link to post
Share on other sites

Posted (edited)

Sorry for not explaining me better.

How can I hide an object if a particular portal row is empty?  In my test file I want the arrow to hide if portal row 3 is empty.

Thanks

 

Test File.fmp12

Edited by Gilbert13

Share this post


Link to post
Share on other sites

In your test file, portal row #3 is not empty. It is occupied by the third out of four related records. Only the Text field of the record shown in that portal row is empty. As I said earlier, you can tell it's empty because the expression:

IsEmpty ( GetNthRecord ( Child 0::Text ; 3 ) )

evaluates as true. And as I said earlier, there is a big red flag waving over this request.

Share this post


Link to post
Share on other sites
21 hours ago, comment said:

I must add that your question raises some red flags regarding your structure. Why do you need numbered fields in the parent table?

Gilbert13, Comment asked a question and you never answered him.  If you don't answer our questions, we will be unable to help you properly.  :-)

As a matter of fact, you never responded to Lee either.  You are telling us what you want but not WHY.  What is the reason you want this?  Now you have two questions.  :wink3:

Share this post


Link to post
Share on other sites

I did not explain myself correctly, thank you all for helping me you all do an excellent job for the FM community.

Comment your suggestion works perfect for what I am trying to do.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now