Order entry works fine but our service connect workflow that calls the MasterUpdate method is failing because IncotermCode can’t be null. I don’t understand why we should be forced to pass in an empty string to a field that is not required. I can see that when the UI calls the master update method, that is what it is doing (passing an empty string). But there are other fields in OrderHed we don’t have mapped in the service connect workflow at all and none of those cause a failure. Struggling to understand how a field can be required but not required.
Incoterms is new so I suppose we might see some oddness, sorry you are dealing with that. Let me go on record stating I am very happy we have incoterms now.
3 Likes
I suspect the field is setup on the Db as notnull passing an empty string should fix it
Or just mapping the dataset link through assuming you did a GetNew etc
Probably but I resent having to change anything in legacy service connect just because they added a new field.
1 Like
Hard to say what’s right and wrong in this case. They listened to an idea and implemented something that caused a slight change to the master update method.
Did you put in a case on this issue?
1 Like
Try doing a PreProcessing BPM on MasterUpdate and set the field there see if it helps.
Do you even know me?
I don’t know if we had the pleasure of meeting at insights last year, did we? I apologize if we did and my memory is letting me down 
1 Like
But based off of this forum I know you are active with support and always bringing the issues to light and that’s huge for all of us.
I can’t remember either lol, I just meant from the forum. Of COURSE I entered a case. Haven’t heard back though. And I am trying to avoid touching the service connect if at all possible.
I had to meet her in a class. She decided not to show up and drink with us… 
Next year I promise
Par for the course when it comes to Service Connect and upgrades… During an upgrade I just go into every SC workflow conversion node and drag the lines over for any new field that shows up in the dataset… you never know when there is going to be some code that trips up over nulls…
2 Likes
So interestingly, assigning a literal empty string to IncotermCode works, but assigning it to IncotermLocation still fails. But in the UI the incoterm location field is disabled so its even less logical for that field to be required.
I’ve tried a string functoid and having that be “” and I’ve also tried setting the literal to “”. Do you perhaps remember how you resolved this error? Thank you for your time.
1 Like
Read the Activity Log wrong. Doing below worked. One of my conversions wasn’t wired back up after I did below. So the value was lost.
Mondays, ammirite!?
2 Likes