
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-14-2020 07:56 AM
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!
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2020 11:33 AM
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-03-2024 06:36 AM
Hi @Jayarnab Saha I am experiencing the same issue. I have exported and imported the rate lines and only the existing rate lines are updating but new rate lines are not created.
Please can you assist?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2020 11:33 AM
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!