Business rule doesnt work while data import

[mankali_kal]

We have a business rule that automatically generates asset tags for assets.

When adding an asset through the form, the numbers generate correctly. However, when bulk-loading assets using an Excel sheet, the business rule sometimes doesn’t trigger, or it generates duplicate asset tag numbers.

It seems that the transform map is not correctly recognizing the database operations.

Has anyone encountered a similar issue or have any suggestions?

Thanks

[mankali_kal]

Helllo @Robert H ,

Thanks for your response,

I’m not currently aware of any risks associated with using the numbering system. Do you foresee any potential concerns?

My requirement is to bulk load asset information, automatically generate asset tags, and send a response back to the requester with the generated tag numbers.

If there are no identified risks with this numbering approach, I’m comfortable proceeding, as it would meet the requirement effectively.

[mankali_kal]

I would like to mention that we are working in domain seperated instance. Numbering system seems to be a global configuration. Any alternative to achieve this in domain specific instance?

[Robert H]

Hello @mankali_kal ,

I'm not seeing any conflict in using the built-in numbering feature together with domain separation. Many applications, like Incident Management, use this feature and at the same time support domain separation.

But, as with all changes, this should be tested thoroughly in a non-production environment to make sure there are no undesired side effects.

Regards,

Robert

[mankali_kal]

Hi @Robert H ,

I tried the number maintenance concept and applied it to asset_tag attribute. But it seems like everytime a number is skipped while bulk loading the data.

attached the screenshot for reference. I checked deleted records and did not find anything. Tried loading the data multiple times but the same behavior everytime. 

Please assist.

Thanks,

[Robert H]

Hello @mankali_kal ,

There are several reasons why this might happen.

For example, by default numbers are also assigned if you just initialize a new record without saving it to the database, see here. There is a System Property "glide.itil.assign.number.on.insert" that you could try setting to "true", but please note that this has a global impact on all tables that use auto numbering.

You also mentioned earlier that this is a domain separated instance, so it could be that someone created an asset with ASTG0001049 in domain A, then someone else created an asset in domain B, so the next asset in domain A got the number ASTG0001051.

Try creating a few assets manually very quickly. If there are no gaps in the numbering then your bulk import is the reason for what you observed.

Regards,

Robert