Selecting and adding multiple records in the custom detail in custom section.
I have read this article regarding adding multiple value to a detail.
Link - https://academy.creatio.com/documents/technic-sdk/7-15/adding-multiple-records-detail
But I do not understand these variable values. The opportunity and contact are the sections that are already created in the system. I want to know what values should I put in custom detail schema.
Details of Objects (every object is custom) -
- Client section with a detail of Partners
- Partners detail is made from Partner section
I want to change the Partner detail in Client to add multiple records. But I do not understand what should be the values of rootEntitySchemaName, rootColumnName, relatedEntitySchemaName, relatedColumnName.
Can anyone please help in this matter?
Thanks
Ram
Like
Hello Ramnath,
rootEntitySchemaName is the name of the parent object. This is likely the object for the page where the detail is located, so if the detail is on the Account page, this would be Account
rootColumnName is the name of the column on the detail object that relates it to the parent object. In the example of being on the Account page, this would be the name of the column on the detail object that is the account lookup, such as UsrAccount
relatedEntitySchemaName is the name of the object you're looking up to add to the detail. So, if the lookup is looking up contacts, this would be Contact
relatedColumnName is the name of the column on the detail object that the result from the lookup is stored in. So in the example of looking up contacts, this would be a contact lookup on the detail object, such as UsrContact.
Maybe this article will help? https://customerfx.com/article/adding-to-a-detail-from-a-lookup-in-crea…
Ryan
Hello Ramnath,
rootEntitySchemaName is the name of the parent object. This is likely the object for the page where the detail is located, so if the detail is on the Account page, this would be Account
rootColumnName is the name of the column on the detail object that relates it to the parent object. In the example of being on the Account page, this would be the name of the column on the detail object that is the account lookup, such as UsrAccount
relatedEntitySchemaName is the name of the object you're looking up to add to the detail. So, if the lookup is looking up contacts, this would be Contact
relatedColumnName is the name of the column on the detail object that the result from the lookup is stored in. So in the example of looking up contacts, this would be a contact lookup on the detail object, such as UsrContact.
Maybe this article will help? https://customerfx.com/article/adding-to-a-detail-from-a-lookup-in-crea…
Ryan
Ryan,
Thanks for helping me out.
Please guide me in this situation more.
Overview of whole scenario
I created a custom detail in a custom section. I have created a Section Contacts (neither base object nor replacing object, It is custom made) and Clients Section. Clients section has a detail Contacts. The detail's object name is the Contacts section.
Section Page - UsrClients
Detail object - UsrContacts (has lookup of UsrClient for connecting record to UsrClients with other inherited columns present in UsrContacts)
Now the name will be
rootEntitySchemaName - UsrClients (section page object name)
rootColumnName - UsrClient (the referencing lookup present in UsrContacts)
relatedEntitySchemaName - UsrContacts (Section page from where records will be read)
relatedColumnName - UsrContact (lookup present in detail)
Now the problem is how can I create a lookup pointing to the same object on which detail is build.
Lookup points to UsrContacts and detail is also created on UsrContacts.
RAMNATH SHARMA,
The detail should be a separate object. Like in the example on the academy, OpportunityContact object on which the detail is built on contains Opportunity and Contact columns. In your case, you would need to create a separate object for the detail that would contain UsrClients and UscrContacts columns, and build the detail on this object.
Dennis Hudson,
Yes, you are right. I have created a new object with 2 looks fields to add this functionality. And it works.
Thanks