Cannot import new rate lines for a Rate Model

User147276 · ‎01-14-2020

We are using the Rate Model and the documentation says that I can update existing rate lines, via the export/import functionality built in the Rate Model. Documentation also says can create new rate lines that append to the model via the import functionality.

Neither of those work for me. When I export the rate lines and update the end dates on all 164, then upload, only 1 will be updated. The rest of the lines are ignored.

Creating new lines via the import functionality doesn't work either. I get errors. We have 4 attributes and those fields do not get updated when we import new lines.

Has anyone successfully updated multiple existing rate lines via the export/import functionality? Has anyone added new rate lines via the import?

I have had to manually create every line and have 200+ more that need to be added to the model. Please help! Thanks!

User147276 · ‎02-18-2020

Wanted to let everyone know what the solution is for this issue. I opened a HI ticket and worked through this with someone there.

After you set up the rate model, the first time you need to adjust it or append new lines to it, you will need to do the following: (copied from my HI ticket)

Set the system property "glide.import_set_row.dynamically_add_fields" to true. sys_properties table
Specifies whether an import set can add new columns to the staging table (true) or not (false). Instances that contain large numbers of import sets can sometimes become unresponsive when an import adds a column because the instance must alter every row in the staging table. Sometimes the database alter table action causes an outage. Setting this property to false prevents an import set from adding columns to the staging table and produces a log message.

NOTE: This is a really scary property if you have integrations, etc. We have it set to FALSE in our prod instance.

More info from the HI ticket:
Rate Line Import is a combination of update Rate Line and Rate Line Attributes. The staging table 'imp_rate_model_line' is having cloned fields aligned with 'rate_model_line' and the attribute fields needs to be get added dynamically based on exported file's columns. For this reason, 'glide.import_set_row.dynamically_add_fields' property should be TRUE. In case, setting this property to TRUE for all the import is costly, then follow the below workaround.

1. Set the 'glide.import_set_row.dynamically_add_fields' to TRUE.
2. Import Rate Line with the attributes column once (with single row also fine).
3. Set back the 'glide.import_set_row.dynamically_add_fields' to FALSE. This will create the necessary dynamic fields in staging table on the first import.

So, from next time onwards it's not required to have dynamically added fields to staging table. But, if you have any new attributes added for Rate Line Attribute, then the above steps should be executed once again.

NOTE: We set the system property to True, did one update/import and then set it to False. Afterwards, I did daily rate line imports to update existing rate lines and append new rate lines to the table. Worked great every time!

View solution in original post

User147276 · ‎01-17-2020

Noah,

Have you gotten it work in an instance? Importing rate lines to append to an existing rate model or even updating the existing lines via the import feature?

Jayarnab Saha · ‎01-19-2020

Hi @tcodell

Please try the below steps in your instance and let me know what errors you are getting.

1. Go to rate_model_line table, filter few Rate Lines (suggesting 4-5 rate lines, for better troubleshooting).

2. Export this filtered rate lines as .xlsx.

3. Edit your desired fields and save. Also, you can add a new row for create rate line.

4. Navigate to 'Import Rate Line' UI page -> upload your .xlsx file -> submit -> Run transform -> transform -> Transform history -> open the latest record -> switch to 'Import Log' tab.

5. You can see the reasons of record insertion error.

The error messages are self defining, which will help you to solve the errors. If you find no errors or difficult to understanding the error, please share here.

User147276 · ‎01-21-2020

Thanks for reaching out. Attached is my export of 7 rate lines, and then I attached my import file, so you can see that I added 2 rate lines and updated the cost on 7.

If you look at my file, you'll see that every line has the same set of dates, but 4 different attributes that make it unique. The import log of errors, says that my "same set of attributes cannot have overlapping effective dates". If you look at my attachments, you'll see that every rate line has it's own set of attributes.

Also, the 2 new rate lines that I put in, with obviously 4 different attributes, didn't import.

This is why I'm saying that the import doesn't work.

Thoughts? Or, should I open a HI ticket to get help?

Jayarnab Saha · ‎01-23-2020

Rate line import is working fine with me and this excels also looks good.

This is looking like some data issue in your instance. You may raise a ticket to find the troubleshoot.

Thanks

User147276 · ‎01-27-2020

Thanks for looking at this! I will go ahead and open a HI ticket.