Database Load Generation

• 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

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.

Hi Michael, I am on the latest version (1.2.1) and the issue above is still happening for me. Changing the deleteSettings value in the DG_TABLE table with the text "null" rather than null value is solving the issue for me.

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

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

Hi Michael, I am on the latest version (1.2.1) and the issue above is still happening for me. Changing the deleteSettings value in the DG_TABLE table with the text "null" rather than null value is solving the issue for me.

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.