What's new in Customer Journeys?

Connect and learn more!
HDL Import - Is it possible to validate DefaultExpenseAccount given in Worker.dat — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

HDL Import - Is it possible to validate DefaultExpenseAccount given in Worker.dat

Received Response
34
Views
1
Comments

Summary:

When sending a MERGE using Worker.dat for an existing employee, if we send invalid combination for DefaultExpenseAccount, HDL load doesnot show any error and existing ExpenseAccount data get erased for the employee. Is this the expected behaviour?

Is there any out of the box functionality or any work around to impose validation prior to merging the data

Content (required):

Is there any out of the box functionality or any work around to impose validation for code combination prior to merging the data

Version (include the version you are using, if applicable):

23B

Code Snippet (add any code snippets that support your topic, if applicable):

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!