- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2022 02:13 AM
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
Solved! Go to Solution.
- Labels:
-
Scripting and Coding
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2022 05:51 AM
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 :
Businnes rule :
Here the test when business rule is inactive :
as you can see there is two records : The extra empty record.
Now after activating the business rule :
if it meets your needs, change only the conditions that allow to identify well the empty record.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2022 05:51 AM
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 :
Businnes rule :
Here the test when business rule is inactive :
as you can see there is two records : The extra empty record.
Now after activating the business rule :
if it meets your needs, change only the conditions that allow to identify well the empty record.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2022 12:24 AM
this worked, thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2022 02:01 AM
happy it worked for you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-07-2022 01:06 PM
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.