Hi Mark,
This is part of a tenant login system I am setting up. It's kind of unique. Whenever a Company, Accountant, Staff member, etc. gets created, I add this user to a Master Login user file if it does not exist in the Master user file
Therefore I end up with one user login, one password across all tenants, but that Master user can have access (where permitted) to any tenant, company, etc..
So my understanding is this should be a peer relationship, and multiple, multiple. Because a Master User can reference for example multiple companies, and companies can have multiple tenants users.
So as I understand it, there is no owner?
Below is the statement I use to create a user in the Master file when creating a company users. I did not see an option to create a reference BO but will try that in a few.
The second problem I have which was another post was the password doesn't get updated in the new Object.
If I can get these two pieces to work, the tenant system will work great.
Note:AllTenantUsers (AllSystemUsers) is master login list.
If NOT(EXISTS AllTenantUsers WHERE (AllTenantUsers.EmailAddress=MainCompany.Email)) Then
CREATE AllSystemUsers WITH AllSystemUsers.EmailAddress=MainCompany.Email,AllSystemUsers.FirstName=MainCompany.FirstName,AllSystemUsers.LastName=MainCompany.LastName,AllSystemUsers.LoginName=MainCompany.LoginName, AllSystemUsers.Password=MainCompany.Password, AllSystemUsers.AccessLevel='CompanyAdministrator'
So you are saying add the reference in here. Will take a look. Additonal feedback appreciated now that you can see what I am trying to do and what do you think about the password issue?
Thanks,
Mark