We have a client for whom we perform Excel imports of products into quotes. This import process includes a validation step where the system checks the PartNumber to verify if the product already exists. If it does, the corresponding ID is assigned to the product in the quote. If it does not exist, a new product is created with the appropriate classifications.
However, we discovered that when the PartNumber in the Excel file contains "00", Creatio is unable to process it correctly and instead associates a product with no PartNumber assigned.
Can you help us resolve this issue? Any suggestions would be appreciated!
I recommend that you make sure that the type of the PartNumber field in Creatio matches the format you are trying to insert, i.e. it should be a text field.
In addition, the system has a lookup “Excel import log”, we recommend that you search for your import logs, if there were errors with filling in the column, they will be displayed in this lookup.
If you cannot solve the problem yourself, we recommend contacting our support team for a more detailed check. (support@creatio.com)
I am importing data through Excel into my custom section and attempting to auto-calculate a field based on two other fields in the UI. However, since the user won't be opening the form page, the business rules and JavaScript code I've written aren't being triggered .
I also wrote an" Oninserting" entity event layer code, the same is not getting triggered as well,however the entity event layer code is getting triggered on click of the new button. How do i approach this?
Please describe in more detail what code you wrote (if possible, provide an example), what it is for, and how it's connected to business rule and import.
We need to import lookup values in more than a language from an Excel file.
We have an Excel with two columns: Name (italian) and Name (english).
When we import from Excel the Name column goes into the "current language" lookup name but we want to import the names in two different languages (both active in Creatio) without duplicating them.
You need to import values into two different objects. Let's take [Lookup] for example.
When you import the values for the English culture, you can import directly into [ObjectName] (Lookup in our case) and can only have two columns: Id of the record and the actual Value.
When you import the values for Italian Culture you need to import into Sys[ObjectName]Lcz ( SysLookupLcz in our case) and you need 3 columns: Id of the record - mapped to RecordId, CultureId and the Actual Value.
So the idea is if I import a contact with name Dean, the existing contact with the name Dean will be updated with data from file and no duplicates will be created.
