conflict of customer fields on the test and productive tenants

[Former Member]

Halo everybody,

in the productive tenant there is a SAP screen with customer specific fields, which have been added not in a solution, but by the key user in system.

Theese fields are not visible in the test tenant, though the test tenant has been created as a copy of the production tenant after theese customer fields have been added. Does anybody knows if it is a correct attitude that we can't see customer fields in the test tenant?

Now my main question. We are developing on the test tenant, and we have added some customer specific fields to the SAP screen in our solution. If we upload this solution to the productive tenant, will the customer fields that are already present on the production tenant in the same SAP screen be deleted?

Best regards,

Leonid Granatstein

[Former Member · Accepted solution]

For the first question: yes, the field added by key user are available only in the system where they are specified.

For the second question: no, the old fields will not be deleted.

[Former Member · Accepted solution]

Thank you, Mr. Iannacci!

[HorstSchaude · Accepted solution]

Hello Leonid,

If you want to use fields created by the key user in the SDK you need to map them via the item "References to Customer-Specific Fields".

Here you can specify which fields shall be available in the SDK.

Be careful: If you deploy the solution to the prod / test system you need to create those fields with the same name, type, ... manually in advance before deploying the solution.

As fields created by the key user are tenant-specific they are not part of a tenant copy neither are they deleted if you deploy a solution (as Alessandro mentioned).

bye,

   Horst

[Former Member · Accepted solution]

Hello Horst,

strangely enough I just found those customer-specific fields on the test tenant. The goal is that they are not visible by the development user there, but only visible by the normal business user, as if they would belong to some solution which is not maintained by the developer user who doesn't see them therefore. This fact conters your statement that customer specific fields are tenant-bound and are not copied to the another tenant. What would you say about that?

Another question: what is the behaviour of the Customer Specific Fields, which are referenced by the SDK in the test tenant, but already exist in the productive tenant. To deploy a solution there is no need to create them "manually in advance" on the prod tenant since they exist there already. The question is whether datas in those fields will be resetted when the solution wil be deployed to the prod tenant?

Regards,

Leonid

[Former Member · Accepted solution]

Hello Alessandro,

strangely enough I just found those customer-specific fields on the test tenant. The goal is that they are not visible by the development user there, but only visible by the normal business user, as if they would belong to some solution which is not maintained by the developer user who doesn't see them therefore.  But there are no solutions on the test tenant, so they can't belong to any solution. This fact conters your statement that customer specific fields are tenant-bound and are not copied to the another tenant. What would you say about that?

Regards,

Leonid

[Former Member · Accepted solution]

That's true, but if you need these fields in your solution you can refer to them with the object "References to Customer-Specific Fields"

[HorstSchaude · Accepted solution]

Hello Leonid,

Reg. the second question:

With the "References to Customer-Specific Fields" it is just a reference.

I.e. It makes those field available in the SDK. It does NOT modify the data itself.

But of course it requires that those fields exist.

HTH,

   Horst