Empty record gets created with record producer

Jonas VK
Tera Guru

Hi all, 

I have this strange issue that every time I use my record producer to create records, it will always create an empty record.
The other records also get created but with an error of duplicate key because of it.
I can't seem to figure out where it comes from, and I wonder if anybody could have some tips on tracking where this comes from. 

this is a record that always gets created
find_real_file.png

1 ACCEPTED SOLUTION

Hajar BENJAHHAR
Mega Sage

Hello, 

An empty field will be always created because there is no mapping except the script  you have shared. 

So I propose this solution for your requirement : 

  Create a business rule that delete the empty record.

For my case I create a record producer that points to the incident table : 

find_real_file.png

Businnes rule : 

find_real_file.png

find_real_file.png

 

Here the test when business rule is inactive : 

find_real_file.png

as you can see there is two records : The extra empty record. 

Now after activating the business rule : 

find_real_file.png

if it meets your needs, change only the conditions that allow to identify well the empty record. 

 

View solution in original post

13 REPLIES 13

Hajar BENJAHHAR
Mega Sage

Hello, 

An empty field will be always created because there is no mapping except the script  you have shared. 

So I propose this solution for your requirement : 

  Create a business rule that delete the empty record.

For my case I create a record producer that points to the incident table : 

find_real_file.png

Businnes rule : 

find_real_file.png

find_real_file.png

 

Here the test when business rule is inactive : 

find_real_file.png

as you can see there is two records : The extra empty record. 

Now after activating the business rule : 

find_real_file.png

if it meets your needs, change only the conditions that allow to identify well the empty record. 

 

this worked, thank you

happy it worked for you 

JWayner
Tera Contributor

I've had the same issue. It creates the extra record no matter what (if you remove mapping or deactivate the fields entirely). The problem with using a before business rule to abort a record that is empty is that it still uses the next record number, so your records will look like they skip a number every time you submit.