Sage 100

 View Only
  • 1.  Pardon me for being a moron but what purpose does

    Posted 04-20-2012 08:31
    Pardon me for being a moron but what purpose does ""skip source data truncation"" serve in VI?


  • 2.  RE: Pardon me for being a moron but what purpose does

    Posted 04-20-2012 08:42
    I think it just means that you know you'll be truncating data if you import into a smaller field and you are OK with that... so the job won't warn that data is being lost.


  • 3.  RE: Pardon me for being a moron but what purpose does

    Posted 04-20-2012 08:46
    It appears as if VI has made some type of change. Customer was importing to AR_Customer and in some cases the customer name was over 30 characters. Now if the customer name exceeds 30 we get a FAIL on the import and warning that the customer name is greater than 30 characters. Nothing appears imported for that field. I tried clicking the ""skip source data truncation"" and it did not change the results - still warned if the field is longer than 30. Of course I don't trust most of these ""test"" imports as many times the test provides a false warning...... Seems like Sage made some type of change where it skips data larger than the field size instead of truncating? At least on the customer name field.


  • 4.  RE: Pardon me for being a moron but what purpose does

    Posted 04-20-2012 08:49
    Awesome...another change to make the system better that actually makes it harder to get things done. If you manually set the source length to 30 in the import will that let it through?


  • 5.  RE: Pardon me for being a moron but what purpose does

    Posted 04-20-2012 08:50
      |   view attached
    Apparently, you are allowed to import records that exceed the length of the data dictionary record. I would expect this to cause wierd results. Maybe Alnoor or a techier person than I can add to the conversation.


  • 6.  RE: Pardon me for being a moron but what purpose does

    Posted 04-20-2012 08:53
    It was a simplish workaround -- MID( value, 1,30) worked - evern on strings under total of 30. I've always seen that it appeared to truncate without error


  • 7.  RE: Pardon me for being a moron but what purpose does

    Posted 04-20-2012 08:53
    Hmm - I tried clicking that option and it did not appear to do anything. Maybe the job didn't get trigger for a rebuild simply by clicking on that box?


  • 8.  RE: Pardon me for being a moron but what purpose does

    Posted 04-20-2012 08:54
    I'm with you Wayne, it just truncated before.


  • 9.  RE: Pardon me for being a moron but what purpose does

    Posted 04-22-2012 17:40
    In BF, you can do something like this. In Company Maint / Email tab the SMTP User Name only allows 30 chars. I needed 32 and I think @JohnBroadfoot needed more for his client. Via DFDM I could exceed the dict length of 30. Unless the MAS code specifically does a MID(value,1,30) I will be just fine and so far I have been fine. (Side note: Upgrading to MAS 200 SQL 4.45 and 4.50 will truncate everything after 30) So ""Skip Source Data Truncation"" is not worded well. It means allow the Customer Name to import more than 30. Assuming it works (I don't know never tried) it should PASS a 31 char customer name with a warning as opposed to a FAIL.