DMT Payroll Employees

Yahoo Archive
1
>>Still a few stragglers that probably fit into some strange constraint
These are probably not related to your current problem
- Just a couple other quirks I remembered.. that you might run into too

When viewing a templates details in Excel (thru the DMT interface, just before committing the upload)...
--- Took a while for me to realize records were being modified and saved by Excel.
------- the interface gives no indication but Excel might "guess" at the datatype and reformat some records
------------- e.g. my source file was having it's leading zeros removed from a VendorID column

After one Excel upgrade I had problems with special characters in notes
--- e.g. diameter Ø,  plus/minus ±, etc...
------ I had to play with Excel's encoding to get these working again
2

I am working on DMTing payroll employees into 10.0.700.3 from Vantage 8.03 and I am running into 2 problems.


The first is that the supervisor doesn't exist since they are part of the same file but I am hoping that once my second problem is fixed, multiple runs of the DMT will take care of this.


The other problem is that for a handful of employees I get a "String or binary data would be truncated.  The statement has been terminated" error.  I have been through all the fields and I don't see any string fields that are too long. 


Has anyone else run into this?


Mark

3
>>String or binary data would be truncated.
Sounds like something I had happening once
A few DMT rows would choke even though all the fields seemed to match the size in the data dictionary.

When I manually entered one of the failing records I found received an error message that revealed a constraint in the program.

In my case, I ended up shortening a few descriptions to get by that error.

 
4

When I was heavy into DMT before we went live I ran into something like this a couple times.   The issue was trailing spaces that were not apparent on fields that were used in an index.   In the spreadsheet I was using to import I ran a formula on all the cells to truncate out the trailing spaces.  Try saving the spreadsheet as CSV and opening with Notepad and things like this are easier to spot.  I also got in the habit of checking any name or address fields (especially on customers) by adding a Len() function column to display the length and conditional formatting the column to show those over the max in red.  On big ones with several thousand rows this was a lot more accurate than eyeballing them.

-Todd C.

 

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, August 26, 2015 11:59 AM
To: vantage@yahoogroups.com
Subject: [Vantage] DMT Payroll Employees

 

 

I am working on DMTing payroll employees into 10.0.700.3 from Vantage 8.03 and I am running into 2 problems.

 

The first is that the supervisor doesn't exist since they are part of the same file but I am hoping that once my second problem is fixed, multiple runs of the DMT will take care of this.

 

The other problem is that for a handful of employees I get a "String or binary data would be truncated.  The statement has been terminated" error.  I have been through all the fields and I don't see any string fields that are too long. 

 

Has anyone else run into this?

 

Mark

5

I didn't see anything in notepad so I used notepad++ and found some "record separators".  Once I removed those, most of the records imported fine.  Still a few stragglers that probably fit into some strange constraint in the emergency contact. 


Thanks for the help both of you.