Database Load Generation

With that change you won’t have the problem going forward. I have submitted a new version to app market that will make it so you don’t have to apply this change manually.

Thanks Michael. I deleted the table, configure it again and it is now working with the updated code.

Is this only happening on new install? I will relay this information to other teams but want to make sure if they will also be affected if upgrading to v1.0.8

I should have been more specific, the deleteSettings will fix it for new tables that are added. For any existing ones you should set them manually to null of the delete setting is none.  Otherwise use the trash can link to confirm the delete settings.

Hi Michael, adding deleteSettings: "null" did not fix it. I also tried null without quotes and {}.

I'll just check the Master and set Delete Settings column to {}for now while waiting for the next version. 

Thanks

It's a known bug.  Add the bold below line into rule!DG_CreateNewTableType

deleter: {
  deleterTypeId: 1
},
deleteSettings: "null",
rowWeighting: 0,

I'll release a new version soon.

It is a new install

Was this an upgrade from a previous version?

My initial test failed. It only worked after I checked the json Master and put {} in the Delete Settings column. Is there an instruction on how to use these fields? Thanks.

• Added configurable number of values in each database insert statement using DG_NUMBER_VALUES - reduces size of DB audit log when inserting high volumes of records