I have a field (field A) that defaults to a value. I also have a dynamic rule that says when the default value is present for Field A that another field (Field B) is to be made required, otherwise Field B is not required. I have no other dynamic rules that govern the requirement of Field B. When I select another selection for Field A other than the default value, Field B stays required and I can not save with because the dynamic rule still seems to think the default value is in place. Is the default functionality adversely affecting the dynamic rule for making a field required? Shouldn't these dynamic rules be acting dynamically vs having to save the record for the change to take affect.
This dynamic rule worked fine with the default value up until recently. Is this a new bug in the dynamic rules working with default values?
------------------------------
George Bramhall
------------------------------
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.