[jimk]

We are starting to use Dell Boomi as an ETL to move transaction records from NS to other systems. I made a customer Boomi Status field and put it on our invoice form. I have the default value set to Ready for Boomi, so boomi knows which orders have and have not been processed (the boomi process updates this status once it has been inserted to other system).

What's happening is, when our accountant hits bill on the sales order, it creates the invoice record but that field value is null / blank. However, if she just creates a new invoice (not attached to SO), that field value is filled in.

This field is NOT on the SO record and does not need to be.

Any ideas on how I can get this to work so every new invoice has the ready for boomi field value?

Thanks in advance.
This is a cached copy. Click here to see the original post.

[robert.paulson]

Hi,

Try using a workflow that runs on 'invoice creation' and sets the value of your boomi custom field. Have it run on 'after submit'.

Customization –> Worfklow –> New

Record type: Transaction

Sub type: Invoice

Event Based

Trigger Type: After Record Submit

Save it

1) Click on the State 1 and then on the little pencil icon that appears on the right-end menu

2) Click on New Action –> Set Field Value (you are telling your workflow that you want to set a field value on your invoice once it is created)

3) Under the Parameters section, select your boomi custom field under the dropdown FIELD

4) Under the Value section, click on Static Value

5) Under the 'Selection' you should be able to choose the value 'Ready for Boomi'

For steps 3 to 5, I did a quick example using the class field and the selection field displays the list of classes to choose from

[Olivier Gagnon NC]

It's just a timing issue. Your SOs were created prior to you creating the field and setting the default, so all existing SOs will generate Invoices where the field is empty.

If you created a new SO at this point in time, then invoiced it, you should find that the field properly defaulted.

So you could run a mass update to set the field on existing SOs (the field IS there, it's just hidden, by the way) so that Invoices get the proper value, or, if you only have a few remaining SOs left, just wait till the problem fixes itself.

[Author]

Posts