A few thought from my side
Here is a screen dump
Hi John,
One possible reason why account fields may not be editable is that the object is not created and associated to the person entity. Though I’m not sure if that is what you’re missing or if security is configured incorrectly.
Regarding using inheritance, I’d probably advise against it as Account is already inheriting from User and then you would inherit Account from Person which becomes 2 level and could create overhead when updating this information in the database and there are some security reasons too which are already discussed in this forum post in the past. Looking more closely as to how the application should behave functionally and what sort of data it is going to be could also indicate whether you should use an association.
Hope this helps!
I am still having problems with linking a module entity with the admin.account entity.
So I have associated on a 1- 1 basis Person with admin.Account.
Now I am trying to create a new Person object. I have created a non persisted Registration entity (containing attributes from bothPperson and Account) and in the microflow, create a Person object which is populated by the Registration object.
No problems with attributes that are present in Person BUT when I try to use Registration attributes that correspond to Account, I get an error of “Entity ‘Community.Person’ does not contain attribute ‘Administration.Account.FullName’.” (Where Community is the local module)
So it knows that Registration.Fullname is linked to Adminsitration.Account.FullName but that it is not linked to Person.
So in summary, very confused.