Skip to content


Modifying Nodes Required fields

Wendy l Kennedy asked 1 year ago
We are trying to update the Jobtitle/position field on certain current employees.  I have a spreadsheet with their employee ID and the new Code.  The code is all I want to update, however the required fields on the Employees node include, EmployID, Lastname, first name, social security number, department, jobtitle/position.  I see that I can modify the node and uncheck the ones I do not want but want to make sure it’s ok to do that.  My reasoning is I am being supplied this spreadsheet from a department that does not have access to the SSN and I don’t want to update the name in case they have a data entry error.   Make sense?  Thoughts?
Patrick Roth Staff answered 1 year ago
No – just unmarking the required fields won’t solve the issue.  Fields on GP maps correspond to parameters on the Microsoft eConnect procs that are installed by GP.  Typically required fields on GP maps that are marked as “required” are set that way because the underlying proc doesn’t have a default value.
So while you CAN go into the Node Maintenance in SmartConnect and change that required status, it isn’t going to solve your issue because the proc is going to give an error anyway.
If you essentially have the employee and a new department code, there are two ways to solve this:
1. The easiest way is to just write directly to the employee table in GP.  UPR00100 I believe it is.
You have the employee id and the job title field and could just write directly into the destination table.  Now you don’t need all that other stuff and it can’t change because you didn’t write to the field.
The only thing you would have to be careful of here is that the position field in GP is a validated/lookup field and so if we write direct to table like this, you COULD insert “AAAAA” as your job title which is likely invalid.  So you would want to be careful of that.
2. Use multi data source
If we want to do it by the book at use the Microsoft business logic node, we need all of that extra data.
The easiest way to get that is to use a multi data source map.
In the above example, we don’t have the one bit of information from the vendor – so we use your existing data as one “source” and then a query on the other table (UPR00100 I believe) that would hold the rest of the employee info.
Now when I do my mapping, I have all of the employee existing information with that query and I can map my new field as well as all the “old’ information as well.
I would suggest you map all the fields you have as you want to make sure eConnect doesn’t not re-default the values back to default if they aren’t mapped (which is typically then empty).
I would suggest testing on a test system whichever way you go and verify that the record comes out correctly after the update (should either way).
Wendy l Kennedy answered 1 year ago
thank you, I did the latter but only mapped the required fields (Position is one of them)  It did as you said though, all the other fields were blanked out.  (Address, etc)  Is there a way to avoid this other than mapping each field to the UPR00100 table?

If you would like to submit an answer or comment, please sign in to the eOne portal.