Are you sure this is a conflict between conditional hiding and portal sorting? One way to check this would be to leave the portal unsorted, but sort the relationship, or leave everything unsorted. This would I presume mean that the only thing acting on your portal records would be your conditional hiding.
Hi keywords, when I don't sort the portal, nothing changes. When I sort the relationship the "pink" fields don't show at all.
I see I forgot to mention that I am working with FM13 Advanced
It looks like your Conditional Formatting calculation is based on the context of the parent table instead of on the child table.
1) What is the name of the parent table?
2) What is the name of the child table?
3) What is the formula / calculation you're using for the Conditional Formatting?
Parent table: ProjectHeader
Child table: ProjectUnit
Condition for "pink" fields: ProjectUnit::DATE ENTERED = "" or ProjectUnit::Unit Status ≠ "Confirmed"
Condition for regular fields: ProjectUnit::DATE ENTERED = "" or ProjectUnit::Unit Status = "Confirmed"
I'm using the first condition so that the empty record row does not show in portal.
Is this as it should be?
I'm still a little confused. You're using both Conditional Formatting and Hide Object?
No, not using conditional formatting as that does not allow me to stop editing access to the fields. I apply a different style to the field to make the status (confirmed & no longer able to edit) visible.
That's probably where the issue is coming from. Instead of hiding the field, use access controls (security) to manage editability. It's better not to try to substitute obscurity for security.
Mike, I've marked this as answering my question as it is a better way to go and makes the layout simpler. Though I want to mention, just in case some other novice gets hung up on this, that the issue turned out to be that the conditional fields where not actually on the portal.......