Many times when populating fields in the child form, I make them read-only so they match the parent. The issue I’ve run into is that if it populates a field such as people picker and that user no longer exists, it won’t allow the user to save the child. There’s no indication as to why – it just bumps up to the top of the form. When I troubleshoot, I release the read-only rule to find that the people picker will rightfully not accept the now invalid user.
I’m wondering if there is a way to show the user the indicator that the populated (and read-only) field cannot be validated. Or any other suggestions you may have. Thanks for your time!