Open josedelrio85 opened 2 years ago
@josedelrio85 hmmm. So re-reading the issue, it appears that the client and the tenant API have different behavior when additional fields are added to a sourceTenantId call.
Is that correct?
One workaround is to create the tenant in two steps. Will that not work for you for some reason?
@mooreds Yes, the behaviour differs between a direct API call and the use of the library.
From my point of view, and following the indication in the documentation, I understand that the behaviour of the library function should be corrected.
I really opened the issue to comment on this difference so that you would be aware of it.
I have created a tenant using Tenant APIs using the Default Tenant as a base, but trying to add customisations, in this case email settings.
POST api/tenant
The result is satisfactory, as I get the new Tenant with the default configuration plus the customisations specified in the request.
On the other hand, when using the
CreateTenant
method of the client, if I specify in theSourceTenantId
property the identifier of the base Tenant, the resulting Tenant does not have the custom properties.I understand that this behaviour does not correspond to the behaviour obtained using Tenant APIs and to what is discussed in this section of the documentation: