Microsoft Dynamics CRM (Archived)

How to handle null records

(0) Share

Report

Posted on by crmprogrammer2013

2,665

Hi,

I am writing a custom data import process that imports data from a .csv to CRM.

There are values(child entity) related to the main entity which can be empty or blank. Since I am not checking for any condition and using service.create to create the child entity and associating it to parent entity, it is creating blank child records. In reality, those blank child records should not exist. How do I put condition before creating child record? There are many fields that I need to check for null values in order to prevent blank records. How does it affect checking for null values for so many fields in a 'If' condition?

Or else, can I delete those blank records through some workflow or plugin as they get created through data import process?

Someone please guide me through this.

Thanks for any help.

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (2)

Verified answer

Royal King 27,686 on at

Like (1)

Report

You can go with either restricting creation of record by checking null values or deleting it after creating it in the crm using workflow or bulk delete. You have to test which method performs well. Choose the one that provides better performance.

Was this reply helpful? Yes No
Verified answer

Mahendar Pal 45,095 on at

Like (1)

Report

Hi,

Well you have both the options if you want to modify the code you can write validation to only create record in case specific attributes having value, it will give you more control if you want to implement any other validation as well. It will also avoid doing any extra work.

Otherwise you can simply design bulk deletion job where you can define your record send and let it delete blank records for you.

Thanks

Was this reply helpful? Yes No
crmprogrammer2013 2,665 on at

Like (0)

Report

Thanks guys.

Was this reply helpful? Yes No
Aileen Gusni 44,524 on at

Like (0)

Report

Hi Roxanna

I would prefer do checking first.

Rather than later delete it.

Since checking you just do validation then create the record meanwhile if you create then delete you will need to call 2 times service request to service.create and service.delete as well.

Put a plugin in the child record then throw exception or put the validation in the parent to not create thr child record if your source at first is by cresting the parent then inside the code creating child.

Hope this helps you.

Thanks.

Was this reply helpful? Yes No