Sage 100

 View Only
  • 1.  Need some votes, thanks!! Had a client need to e

    Posted 02-13-2015 13:00
    Need some votes, thanks!! Had a client need to enter a long password but Sage only allows 14 on the Company Maintenance/Email tab. I see that there is a request out there already, here is the link... https://www5.v1ideas.com/TheSageGroupplc/Sage100ERP/Idea/Detail/12867


  • 2.  RE: Need some votes, thanks!! Had a client need to e

    Posted 02-13-2015 13:21
    Had forgotten that this web site still exists... I voted for it.


  • 3.  RE: Need some votes, thanks!! Had a client need to e

    Posted 02-13-2015 14:46
    What version of Sage 100? Possibly there is a tweak you could test then put into play.


  • 4.  RE: Need some votes, thanks!! Had a client need to e

    Posted 02-13-2015 15:34
    Wow, 14 characters isn't enough? Is your client the CIA?


  • 5.  RE: Need some votes, thanks!! Had a client need to e

    Posted 02-14-2015 07:52
    They were trying to make sure it didn't fit on a post-it note...


  • 6.  RE: Need some votes, thanks!! Had a client need to e

    Posted 02-14-2015 09:53
    I voted.


  • 7.  RE: Need some votes, thanks!! Had a client need to e

    Posted 02-14-2015 15:11
    It's a bit silly to limit it to 14 on the screen when the dictionary length is also 14. You see if you enter 14 digits when the password gets encrypted the actual stored length (as encrypted) will be less than 14 because of how the algorithm works. But if you entered 8 then encrypted pswd length may still be 8. Regardless here is a workaround should you choose to engage it.


  • 8.  RE: Need some votes, thanks!! Had a client need to e

    Posted 02-14-2015 15:13
    If you're not on SQL version here is a workaround. Normally I am totally against this idea b/c of data integrity reasons. On 4.50 a customer needed EmailUserID to be 36 instead of default of 30. I saw the field was not used in any other tables. I used DFDM to uncheck the box for Formatted Display (to disassociate the dictionary) then entered the 36-digit value. It expanded the (physical) field for me to 36 while dict length stayed at 30 (this is what Skip Source Data Truncation does in VI). This was OK b/c the field wasn't used elsewhere and they never did any reporting on it (e.g. Company Listing). I made note when they upgrade it would get chopped back down to 30 and I would need to re-do this (unless they upgraded to SQL where it's stuck at 30) If you BACKUP the Sy_Company.m4t file and find the EmailUserIDPassword$ field is not used elsewhere you could try this below. I normally would have said just use same DFDM trick above but problem is you need to put in the encrypted password. So on v2014 I tried V/ just now into Sy_Company (made BACKUP the Sy_Company.m4t file first) using a 20-digit password. Originally I checked the box for Skip Source Data Truncation as it does the expand trick but it doesn't work on this table. So I unchecked it and then it worked. The reason is it encrypted my password first and the encrypted one is only 14 digits! Had I started with 21 unencrypted it may have encrypted to 15 ergo no go. Import Job specifics: * Table Name = Sy_Company * On Data tab use these 3 fields and do a REPLACE on all 3: CompanyKey (from DFDM), CompanyCode, and EmailUserIDPassword$ Note from this point onwards never use the Company Maint / Email tab screen to maintain any changes in password. Always import into it. Also if you upgrade, you'll have to repeat this trick unless they upgrade to SQL and then M/D tricks are needed.


  • 9.  RE: Need some votes, thanks!! Had a client need to e

    Posted 02-14-2015 15:16
    The question now is how long is the unencrypted password assuming your CIA client will let you disclose that info :)


  • 10.  RE: Need some votes, thanks!! Had a client need to e

    Posted 02-16-2015 12:48
    They just needed 16 characters and non-SQL v2013. Thanks @AlnoorCassim. This client is going to set up a separate account just for Sage but this is good to know if it comes up again.