web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Unanswered

PSTL combine GL acccounts error

(0) ShareShare
ReportReport
Posted on by 24
Hi!
 
I am trying to combine two GL accounts in GP 18.5 using PSTL and receive this error:  /Conversion failed when converting the nvarchar value '04-0155-005-5022' to data type int/.  That account is not one of the accounts I am trying to combine.  After receiving the error, the combine process runs a little longer, I receive a message saying it is completed and a report prints showing the accounts are combined.  But both accounts still exist in the GL and both still have the  original transactions.
 
When I try to modify an account number it locks up the entire app server on /The Account Modifier is complete on the System DB/3rd party tables/ message.
 
The PSTL version is 18.2.5.  I have clicked on /RebuildProcs/ in PSTL.  I also ran checklinks on all financial and ran reconcile on the GL.
 
The third party products we have are SmartView, SmartFill, SmartList Builder, Auditor, and Nolan Intercompany.  I have used PSTL account combiner with all of those except SmartView in the past on other systems and had no issue with them.  We do not use FRx or Management Reporter although we did use both at one time.  Neither of those programs are installed on our current server.
 
Can anyone tell me how to track down where this error is originating?
 
Thanks,
Marilyn
Categories:
I have the same question (0)
  • Community member Profile Picture
    24 on at
    Thanks for all the info!

    This helped us get a little further.
     
    Thanks,
    Marilyn
  • lancebrigham Profile Picture
    119 on at
    Hi Marilyn,
     
    Another thing you could try doing is running a DEXSQL.log or SQL Profiler while running the PSTL combine. When you encounter, the last event(s) in DEXSQL.log or SQL Profiler should show you what the offending SQL statement. This should clue into where the issue is. It almost sounds like maybe there's a custom table somewhere that has a column named ACTINDX that isn't actually defined as an INTEGER and is instead CHAR and has account strings in or something. I'm completely guessing though.
     
    The way the combine works is that the process loops through all tables that contain columns of certain names pertinent to accounts. GP assumes the data type is what is expected (ACTINDX is INTEGER, ACTNUMST is a string, etc) so if you have a custom table named SomeCustomTable with ACTINDX defined as a CHAR field and you have account strings in it, that could cause the issue or perhaps a 3rd party did something with defining a table outside of Dexterity containing a column with a name that is scanned as part of this process and isn't defined as GP expects it to be.
     
    DEXSQL.log and/or SQL Profiler would be best bet for next step.
     
    Let me know if any questions.

    Thanks,
    Lance Brigham
    Principal Consultant
    Velosio

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 451 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 428 Super User 2025 Season 2

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 239 Most Valuable Professional

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans