2
1
0

Hi,

We are experiencing an unexpected behavior in a Maestro form.

 

We have a Maestro custom component,that is nested within another custom component and then into a page in a Form. To give a general overview of the role of the two components - they serve the purpose of displaying the information provided in previous pages. This is done by calculation rules that copy values from previous pages (as "return data.desiredField")

So, I have, for example, a field called "Phone number" that just returns the value of the phone number field in one of the pages ("return data.phoneNumber").

However, when I publish the components and look into the calculation script on the form level, I see that the name of the field has been changed with an additional "1" at the end, so it's now "return data.phoneNumber1" even though the reference field's ID is still data.phoneNumber and data.phoneNumber1 doesn't exist as a field.

When I clear out the calculation rule (i.e. delete the contents and save a "blank" rule), it regrabs the code from the custom component and is then correct, but whenever I republish the component again, it comes back to the wrong field ID.

We were wondering whether there is a way we can prevent this from happening. Thanks for any response.

    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      Hi Mateusz, the refactoring of component field IDs to match the context of the container form is automatic, and should never produce a reference to a non-existent ID. Please log a support issue with us and provide the Form Details (from the question mark menu, top right of editor) so we can look at the specific scenario and provide advice.

        CommentAdd your comment...