Jump to content
Sign in to follow this  
TJ53

Recod last modified ... including portal fields?

Recommended Posts

Hi, I have a layout with a portal and need to know when and who was the last one to update any of the fields of the layout - including those in the portal.

I'm using a technique that consists on creating a third relationship (self-join with the child table) and a calculation based on it (please have a loot at the attached file, yellow highlighted field in 1st layout). This seems to work but I would appreciate some feedback or suggestions in case there is some other techinque that is more recommendable. Many thanks!

Update.fp7.zip

Share this post


Link to post
Share on other sites

Why not simply:

Max ( Modified ; Max ( Child::Modified ) )

Then you don't need the extra relationship.

Share this post


Link to post
Share on other sites

Thank you for having a look at this. I created the extra relationship so I can also keep track of the last name (or account) that modified either the parent or a child record, that's why the extra relationship is sorted by mod_timestamp. I have updated the file (attached - please see highlighted fields) ... actually, the extra relationship should be with the parent, not a self-join.

I wonder if this is a correct way of doing this ... thanks again!

Update_v2.fp7.zip

Share this post


Link to post
Share on other sites

If you need the name as well, then I suppose the extra relationship can be useful. It could be slightly simplified, though.

Update_v2.fp7.zip

Share this post


Link to post
Share on other sites

It's not only simpler, but it also evaluates faster. Thank you comment.

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
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use.