Make Attachment required before saving Order

adamk · October 10, 2019, 1:41pm

I am looking to make it mandatory for a customer PO to be attached to a sales order before the order can be saved…is there an easy way to make the system check that there is a least one attachment on the order before can be saved? Can I do that through a BPM on one of the sales order Methods?

Jason_Woods · October 10, 2019, 4:00pm

Extended Properties can set this field as Required.

adamk · October 10, 2019, 4:03pm

that attachment field? isn’t that under the Xref table? I want to make sure they attached a PDF to the sales order before it can save

Jason_Woods · October 10, 2019, 4:14pm

Are you wanting to require a document on the Sales Order?
If so, you will need to allow the saving of the Header, but can prevent a creation of a line with a BPM on GetNewOrderDtl.
This won’t work for converted quotes though.

adamk · October 10, 2019, 4:18pm

We rarely (if ever) convert from a quote so that isn’t and issue. What condition would I put in the BPM for it to throw and error if there isn’t an attachment?

Jason_Woods · October 10, 2019, 4:25pm

In pre-processing use a query to check if there is a related attachment. Then error if not.

danbedwards · October 10, 2019, 4:27pm

I would put a condition on Update and use a condition widget using Number of rows in designed query is more or equal to 1. The query would look at Ice.XFileAttch. If wanting the PO attached at the Header you would use RelatedToFile equals OrderHed and Key1 equals OrderNum. You can join Ice.XFileAttch to Ice.XAttachMetaData to find specific attachment types

adamk · October 10, 2019, 4:31pm

Thanks Guys! Appreciate the help as always

adamk · October 11, 2019, 3:42pm

Hi Dan

So running into one issue…when I try and link the two tables, its throwing an error as OrderNum is and integer, where as Key1 is a string…when I link them in a standard BAQ it doesn’t have an issue, but as soon as its a query within the BPM it doesn’t like it…what am I missing?

Thanks!

danbedwards · October 11, 2019, 4:04pm

I would create a variable within the BPM named OrderNumber as a type string. You can then use a set variable / argument and set OrderNumber to your tt.OrderNum.ToString(). Then in the BPM Query you can just use the variable and this also avoids the pitfalls of having the tt table joined in the query.

adamk · October 11, 2019, 4:38pm

Ok that was the route I was going, but was still getting an error…so I think i am doing something wrong. Compilation error I am getting is:

BPM is set up as such;

danbedwards · October 11, 2019, 4:50pm

Put double quotes around OrderHed in the criteria

adamk · October 11, 2019, 4:53pm

Ok that stopped the error in compiling!

Thanks Dan, appreciate your time!!

ypgpatel · June 1, 2022, 4:42pm

I get this error. Did you as well? If so, how did you fix it?

danbedwards · June 2, 2022, 11:51pm

Take off the ToString() - it appears your OrderNum variable is an int.

ypgpatel · June 6, 2022, 1:25pm

That resolved that issue, but now when I enable to the pre-processing I get this error.

NateS · June 6, 2022, 2:02pm

Whats the code for your condition widget?

ypgpatel · June 6, 2022, 2:05pm

NateS · June 6, 2022, 2:12pm

I see what you were going for. Key 1 is a string, so you wanted to convert your order integer into a string. Which ever way you go, make sure they are all the same datatype all the way through. Take a look at the datatypes for each widget and variable.

ypgpatel · June 6, 2022, 2:16pm

orderNum is set to default type System.Int32