We have 3 account owner shared objects and 6 online account user shared objects.
Each user object includes a nested owner object representing the owner who authorized the user.
User objects include:
user1.leganame(string)
user1.signerbool(bool)
user1.owner (nested object)
Owner Objects:
owner1.legalname(string),
owner1.taxidnumber(strng)
etc…
For each user being setup there is a Select Box to designate which owner is related to the user:
The Select Box datasource is an array of all 3 “accountowner” objects
For the first accountuser being setup for example..:
The “selected value” I setup for the first user’s owner Select Box is accountuser1.owner (object)
When I go in as an application user to setup the first account user and click on the Select Box, all three owner legalnames appear as expected, and when I select one it works fine.
When I click a button to validate that the first user’s required info was all input correctly, the validation works great and gives the appropriate error message.
However, about 1 second later the Select Box’s selected owner disappears and it is reset to the “select an owner” placeholder text. And then, when I type a letter into user1’s legalname text input, the correct owner reappears in the select box. Really strange.
Hello Robert,
I’m working about this topic to see if this issue will be reproduced.
I just want to know the reason of using object for “User”. This is the screenshot to explain my approach:
What I did here is that the User is an entity with a string input (Legal Name), a boolean (Signer Bool) and an object (Owner with an attribute “value” that is shown in the input).
In owners, when I fill the first owner (or two or all owners), it’s inserted inside the selectbox, I did a default selected value with the last owner filled from all owners. The selectbox is bound to an array Qodly Source (collection).
So, as you can see, when I click on the button “validate”, automatically the user that has the legal name “lg1” has an owner “o1”, and the selectbox remains its selected value.
I’m not sure if that’s exactly what you want to do.
I made some other changes relating to the workflow last few days. I will circle back on this issue next day or two. My thought is that if we do the workflow so that the new owners are already added to the DB before we goto this add users page, the Selectboxes will work.
I will follow up with results.
Your approach is what I want to do. Previously, when application user goes through the form, everything was an object until the form was validated and submitted, then all the entities were to be created and saved.
Currently, I am going to have application users: Add the account data to the account object, then validate, save, and capture the id of the saved account. Next, add the owners, validate, save, and capture the ids of the owners. Finally, application users will goto the Account Users setup page to add the authorized account users and connect each with its authorizing owner via select box, then validate and save the users. So 3 pages instead of 1 page. Will see how it goes.
1 Like
