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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Error when searching f...
Finance | Project Operations, Human Resources, ...
Answered

Error when searching for Vendors: [Microsoft][SQL Server Native Client 11.0][SQL Server]Column name or number of supplied values does not match table definition

(1) ShareShare
ReportReport
Posted on by WCJMON 55

Hello all 

We recently upgraded GP 2016 with US 2020 Year End update. Now we seem to be getting the following error in the Search Vendor screen when adding a column definition: [Microsoft][SQL Server Native Client 11.0][SQL Server]Column name or number of supplied values does not match table definition. I enabled the DEXSQL.log and reproduced the error, and it looks to be creating an temp table with several temp SPROCS, ultimately ending up in that error. I'm not familiar enough with the GP backend to find where the mismatch is. 

5265.SQL-Error.pngSearch-Vendors-Screen.png

Categories:
Microsoft Dynamics GP
I have the same question (0)
  • David Musgrave MVP GPUG All Star Legend Moderator Profile Picture
    David Musgrave MVP ... 14,095 Most Valuable Professional on at

    Use the Dex.ini Settings or GP Power Tools to capture logs.

    In particular the DEXSQL.LOG should provide more information about the error and which table is the issue.

    To use GP Power Tools, get to just before the error and use the Tools menu to Start Manual Logging. Generate the Error and then use the Tools menu to Stop Logging.

    To use Dex.ini Settings, Exit GP and update the following settings.

    SQLLogSQLStmt=TRUE

    SQLLogODBCMessages=TRUE

    SQLLogAllODBCMessages=TRUE

    Get to just before the error and Delete the DEXSQL.LOG file in the data folder. Generate the error. Then copy the DEXSQL.LOG to a new name avoid more being added to it.

    Exit GP and change the settings back to FALSE. If this is a terminal server, make sure no one else is using GP otherwise you will get log entries from them too.

    Note using GPPT, means not changes needed to Dex.ini. No exiting needed. Only the current session is recorded.

    Once we have more detail a solution can be worked out.

    Regards

    David

  • Suggested answer
    Derek Albaugh Profile Picture
    Derek Albaugh on at

    As David mentioned, a dexsql.log will show you what script is causing this 'number of supplied values' message.

    Usually this message is indicative of a procedure expecting a different number of columns than a table has, whether more or less, thus the error.

    If you're in SmartList functionality, the ASIEXP81 (SmartList Favorites Master) also gets setup to have a specific number of columns to go along with the account framework maximums setup (as mentioned in SY003001 and SY00302 system tables) and if that table doesn't have the correct columns, it'll also cause this type of message.

    Thanks

  • Beat Bucher GP Geek GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,058 Moderator on at

    Hi,

    As others pointed out, this is likely to be a failure of updating some of the table structures during your last GP upgrade from 2016 to 18.3 version..

    The DEXSQL trace log is likely to point you towards which table will have to be re-created. GPPT has the ability to help you tackle this without loosing data.

  • WCJMON Profile Picture
    WCJMON 55 on at

    Thank you all for your replies. Enabling the DEXSQL was one of the first things I did, but I can't seem to find the table having the issue. I think it might be the PA00001 table as it's empty right now, which makes me think it gets filled during this process. Unfortunately, looking at the log is a little foreign to me as I am not super familiar with the GP table structure (Looks like it's trying to join customer data???). I've attached the log here. I'm hoping it will make more sense to you guys. Thanks again!

    Error-log_2E00_.txt

  • Suggested answer
    Derek Albaugh Profile Picture
    Derek Albaugh on at

    So, the log shows the following:

    BEGIN DECLARE @stored_proc_name char(33) DECLARE @retstat int set nocount on SELECT @stored_proc_name = 'DYNAMICS.dbo.ASI_SP_VENDOR_LOOKUP' EXEC @retstat = @stored_proc_name '##1630130', '', 'CPNYTABLE.dbo.', ' FROM ', 'CPNYTABLE.dbo.PM00200 (nolock) LEFT OUTER JOIN CPNYTABLE.dbo.PM00201 (nolock)  ON CPNYTABLE.dbo.PM00200.VENDORID = CPNYTABLE.dbo.PM00201.VENDORID  LEFT OUTER JOIN CPNYTABLE.dbo.PA00001 (nolock)  ON CPNYTABLE.dbo.PM00200.VENDORID = CPNYTABLE.dbo.PA00001.VENDORID  LEFT OUTER JOIN CPNYTABLE.dbo.RM00101 (', 'nolock)  ON CPNYTABLE.dbo.PA00001.CUSTNMBR = CPNYTABLE.dbo.RM00101.CUSTNMBR ', '', '', '', '', '', '', ' WHERE ', '((UPPER(ISNULL(CPNYTABLE.dbo.PM00200.VENDORID,'''')) LIKE ''%CEM%''))', '', '', '', '', '', '', '' SELECT @retstat set nocount on END

    /*

    /*  Date: 12/14/2020  Time: 10:30:01

    SQLSTATE:(21S01) Native Err:(213) stmt(11937520):*/

    [Microsoft][SQL Server Native Client 11.0][SQL Server]Column name or number of supplied values does not match table definition.*/

    In this script, you can see the PM00200, PM00201, PA00001, RM00101 tables mentioned, so to start, we'd want to verify those tables all have the correct structure for the version and build of Dynamics GP you're currently on.

    The ASI_SP_VENDOR_LOOKUP procedure appears to be primarily looking at PM00200 table.

    Looking at the table changes for the latest update, the PM00200 table does get a new column, VENDDBA, so I'd start with looking to make sure that column exists, even though that column isn't specifically called by the above script.

    community.dynamics.com/.../table-column-and-parameter-changes-in-microsoft-dynamics-gp-october-2020-release-2020-year-end

    Thanks

  • WCJMON Profile Picture
    WCJMON 55 on at

    Checked PM00200 and can confirm that the VENDDBA column is there.

  • Suggested answer
    Derek Albaugh Profile Picture
    Derek Albaugh on at

    Which it should, and if you run a 'sp_helptext ASI_SP_VENDOR_LOOKUP' script, it should show this proc like this, where it does mention the new column: PM00200.VENDDBA.

    This stored procedure can be re-created using the Database Maintenance Utility, to rule that out as well.

    CREATE PROCEDURE ASI_SP_VENDOR_LOOKUP  @temptable varchar(20),  @table varchar(20),  @db varchar(20),  @from1 varchar (254),  @from2 varchar (254),  @from3 varchar (254),  @from4 varchar (254),  @from5 varchar (254),  @from6 varchar (254),  @from7 varcha

    r (254),  @from8 varchar (254),  @from9 varchar (254),  @where1 varchar (254),  @where2 varchar (254),  @where3 varchar (254),  @where4 varchar (254),  @where5 varchar (254),  @where6 varchar (254),  @where7 varchar (254),  @where8 varchar (254),  @where9

    varchar (254) AS  exec('delete ' + @temptable +  ' insert ' + @temptable + ' SELECT ' +  @db + 'PM00200.VENDORID,' +  @db + 'PM00200.VENDNAME,' +  @db + 'PM00200.VNDCHKNM,' +  @db + 'PM00200.VENDSHNM,' +  @db + 'PM00200.VADDCDPR,' +  @db + 'PM00200.VADCD

    PAD,' +  @db + 'PM00200.VADCDSFR,' +  @db + 'PM00200.VADCDTRO,' +  @db + 'PM00200.VNDCLSID,' +  @db + 'PM00200.VNDCNTCT,' +  @db + 'PM00200.ADDRESS1,' +  @db + 'PM00200.ADDRESS2,' +  @db + 'PM00200.ADDRESS3,' +  @db + 'PM00200.CITY,' +  @db + 'PM00200.STA

    TE,' +  @db + 'PM00200.ZIPCODE,' +  @db + 'PM00200.COUNTRY,' +  @db + 'PM00200.PHNUMBR1,' +  @db + 'PM00200.PHNUMBR2,' +  @db + 'PM00200.PHONE3,' +  @db + 'PM00200.FAXNUMBR,' +  @db + 'PM00200.UPSZONE,' +  @db + 'PM00200.SHIPMTHD,' +  @db + 'PM00200.TAXSC

    HID,' +  @db + 'PM00200.ACNMVNDR,' +  @db + 'PM00200.TXIDNMBR,' +  @db + 'PM00200.VENDSTTS,' +  @db + 'PM00200.CURNCYID,' +  @db + 'PM00200.TXRGNNUM,' +  @db + 'PM00200.PARVENID,' +  @db + 'PM00200.TRDDISCT,' +  @db + 'PM00200.TEN99TYPE,' +  @db + 'PM0020

    0.MINORDER,' +  @db + 'PM00200.PYMTRMID,' +  @db + 'PM00200.MINPYTYP,' +  @db + 'PM00200.MINPYPCT,' +  @db + 'PM00200.MINPYDLR,' +  @db + 'PM00200.MXIAFVND,' +  @db + 'PM00200.MAXINDLR,' +  @db + 'PM00200.COMMENT1,' +  @db + 'PM00200.COMMENT2,' +  @db + '

    PM00200.USERDEF1,' +  @db + 'PM00200.USERDEF2,' +  @db + 'PM00200.CRLMTDLR,' +  @db + 'PM00200.PYMNTPRI,' +  @db + 'PM00200.KPCALHST,' +  @db + 'PM00200.KGLDSTHS,' +  @db + 'PM00200.KPERHIST,' +  @db + 'PM00200.KPTRXHST,' +  @db + 'PM00200.HOLD,' +  @db +

    'PM00200.PTCSHACF,' +  @db + 'PM00200.CREDTLMT,' +  @db + 'PM00200.WRITEOFF,' +  @db + 'PM00200.MXWOFAMT,' +  @db + 'PM00200.SBPPSDED,' +  @db + 'PM00200.PPSTAXRT,' +  @db + 'PM00200.DXVARNUM,' +  @db + 'PM00200.CRTCOMDT,' +  @db + 'PM00200.CRTEXPDT,' +

    @db + 'PM00200.RTOBUTKN,' +  @db + 'PM00200.XPDTOBLG,' +  @db + 'PM00200.PRSPAYEE,' +  @db + 'PM00200.PMAPINDX,' +  @db + 'PM00200.PMCSHIDX,' +  @db + 'PM00200.PMDAVIDX,' +  @db + 'PM00200.PMDTKIDX,' +  @db + 'PM00200.PMFINIDX,' +  @db + 'PM00200.PMMSCHI

    X,' +  @db + 'PM00200.PMFRTIDX,' +  @db + 'PM00200.PMTAXIDX,' +  @db + 'PM00200.PMWRTIDX,' +  @db + 'PM00200.PMPRCHIX,' +  @db + 'PM00200.PMRTNGIX,' +  @db + 'PM00200.PMTDSCIX,' +  @db + 'PM00200.ACPURIDX,' +  @db + 'PM00200.PURPVIDX,' +  @db + 'PM00200.N

    OTEINDX,' +  @db + 'PM00200.CHEKBKID,' +  @db + 'PM00200.MODIFDT,' +  @db + 'PM00200.CREATDDT,' +  @db + 'PM00200.RATETPID,' +  @db + 'PM00200.Revalue_Vendor,' +  @db + 'PM00200.Post_Results_To,' +  @db + 'PM00200.FREEONBOARD,' +  @db + 'PM00200.GOVCRPID,

    ' +  @db + 'PM00200.GOVINDID,' +  @db + 'PM00200.DISGRPER,' +  @db + 'PM00200.DUEGRPER,' +  @db + 'PM00200.DOCFMTID,' +  @db + 'PM00200.TaxInvRecvd,' + @db + 'PM00200.VENDDBA' +  @from1 + @from2 + @from3 + @from4 + @from5 + @from6 + @from7 + @from8 + @fro

    m9 + @where1 + @where2 + @where3 + @where4 + @where5 + @where6 + @where7 + @where8 + @where9  )

  • Verified answer
    Derek Albaugh Profile Picture
    Derek Albaugh on at

    So, update.........it turns out this is an issue after upgrading to 16.00.0864, the 2020 YE update for GP 2016, the ASI_SP_VENDOR_LOOKUP procedure in the GP system database, is missing the VENDDBA reference to the PM00200 table.

    You can use the following script to alter this procedure, after making a backup of the DYNAMICS/system database:

    /****** Object:  StoredProcedure [dbo].[ASI_SP_VENDOR_LOOKUP]    Script Date: 12/15/2020 9:44:39 AM ******/

    SET

     ANSI_NULLS ON GO

    SET

     QUOTED_IDENTIFIER OFF GO ALTER PROCEDURE [dbo].[ASI_SP_VENDOR_LOOKUP] @temptable varchar(20),

     @table varchar(20),

     @db varchar(20),

     @from1 varchar (254),

     @from2 varchar (254),

     @from3 varchar (254),

     @from4 varchar (254),

     @from5 varchar (254),

     @from6 varchar (254),

     @from7 varchar (254),

     @from8 varchar (254),

     @from9 varchar (254),

     @where1 varchar (254),

     @where2 varchar (254),

     @where3 varchar (254),

     @where4 varchar (254),

     @where5 varchar (254),

     @where6 varchar (254),

     @where7 varchar (254),

     @where8 varchar (254),

     @where9 varchar (254) AS exec(

       'delete ' + @temptable + ' insert ' + @temptable + ' SELECT ' + @db + 'PM00200.VENDORID,' + @db + 'PM00200.VENDNAME,' + @db + 'PM00200.VNDCHKNM,' +

    @db + 'PM00200.VENDSHNM,' + @db + 'PM00200.VADDCDPR,' + @db + 'PM00200.VADCDPAD,' + @db + 'PM00200.VADCDSFR,' + @db + 'PM00200.VADCDTRO,' + @db +

    'PM00200.VNDCLSID,' + @db + 'PM00200.VNDCNTCT,' + @db + 'PM00200.ADDRESS1,' + @db + 'PM00200.ADDRESS2,' + @db + 'PM00200.ADDRESS3,' + @db + 'PM00200.CITY,'

    + @db + 'PM00200.STATE,' + @db + 'PM00200.ZIPCODE,' + @db + 'PM00200.COUNTRY,' + @db + 'PM00200.PHNUMBR1,' + @db + 'PM00200.PHNUMBR2,' + @db + 'PM00200.PHONE3,'

    + @db + 'PM00200.FAXNUMBR,' + @db + 'PM00200.UPSZONE,' + @db + 'PM00200.SHIPMTHD,' + @db + 'PM00200.TAXSCHID,' + @db + 'PM00200.ACNMVNDR,' + @db + 'PM00200.TXIDNMBR,'

    + @db + 'PM00200.VENDSTTS,' + @db + 'PM00200.CURNCYID,' + @db + 'PM00200.TXRGNNUM,' + @db + 'PM00200.PARVENID,' + @db + 'PM00200.TRDDISCT,' + @db + 'PM00200.TEN99TYPE,'

    + @db + 'PM00200.MINORDER,' + @db + 'PM00200.PYMTRMID,' + @db + 'PM00200.MINPYTYP,' + @db + 'PM00200.MINPYPCT,' + @db + 'PM00200.MINPYDLR,' + @db + 'PM00200.MXIAFVND,'

    + @db + 'PM00200.MAXINDLR,' + @db + 'PM00200.COMMENT1,' + @db + 'PM00200.COMMENT2,' + @db + 'PM00200.USERDEF1,' + @db + 'PM00200.USERDEF2,' + @db + 'PM00200.CRLMTDLR,'

    + @db + 'PM00200.PYMNTPRI,' + @db + 'PM00200.KPCALHST,' + @db + 'PM00200.KGLDSTHS,' + @db + 'PM00200.KPERHIST,' + @db + 'PM00200.KPTRXHST,' + @db + 'PM00200.HOLD,'

    + @db + 'PM00200.PTCSHACF,' + @db + 'PM00200.CREDTLMT,' + @db + 'PM00200.WRITEOFF,' + @db + 'PM00200.MXWOFAMT,' + @db + 'PM00200.SBPPSDED,' + @db + 'PM00200.PPSTAXRT,'

    + @db + 'PM00200.DXVARNUM,' + @db + 'PM00200.CRTCOMDT,' + @db + 'PM00200.CRTEXPDT,' + @db + 'PM00200.RTOBUTKN,' + @db + 'PM00200.XPDTOBLG,' + @db + 'PM00200.PRSPAYEE,'

    + @db + 'PM00200.PMAPINDX,' + @db + 'PM00200.PMCSHIDX,' + @db + 'PM00200.PMDAVIDX,' + @db + 'PM00200.PMDTKIDX,' + @db + 'PM00200.PMFINIDX,' + @db + 'PM00200.PMMSCHIX,'

    + @db + 'PM00200.PMFRTIDX,' + @db + 'PM00200.PMTAXIDX,' + @db + 'PM00200.PMWRTIDX,' + @db + 'PM00200.PMPRCHIX,' + @db + 'PM00200.PMRTNGIX,' + @db + 'PM00200.PMTDSCIX,'

    + @db + 'PM00200.ACPURIDX,' + @db + 'PM00200.PURPVIDX,' + @db + 'PM00200.NOTEINDX,' + @db + 'PM00200.CHEKBKID,' + @db + 'PM00200.MODIFDT,' + @db + 'PM00200.CREATDDT,'

    + @db + 'PM00200.RATETPID,' + @db + 'PM00200.Revalue_Vendor,' + @db + 'PM00200.Post_Results_To,' + @db + 'PM00200.FREEONBOARD,' + @db + 'PM00200.GOVCRPID,'

    + @db + 'PM00200.GOVINDID,' + @db + 'PM00200.DISGRPER,' + @db + 'PM00200.DUEGRPER,' + @db + 'PM00200.DOCFMTID,' + @db + 'PM00200.TaxInvRecvd,' + @db + 'PM00200.VENDDBA'

    + @from1 + @from2 + @from3 + @from4 + @from5 + @from6 + @from7 + @from8 + @from9 + @where1 + @where2 + @where3 + @where4 + @where5 + @where6 + @where7 + @where8 + @where9

     ) GO

    Once you do this, make another backup, then launch GP 2016 and see if this doesn't resolve this error for you on looking up vendor IDs.

    You can let us know either way, as others will run into this as well.

    Thanks

  • WCJMON Profile Picture
    WCJMON 55 on at

    That's it. Looking at that SPROC, I don't see any reference to that column. I'll need a maintenance window to correct it, but that definitely would cause the error we're seeing. I'll let you know, once I run the update script.

  • Verified answer
    Derek Albaugh Profile Picture
    Derek Albaugh on at

    Here is an updated script, we found a couple issues with the previous one, use this one:

    /****** Object:  StoredProcedure [dbo].[ASI_SP_VENDOR_LOOKUP]    Script Date: 12/15/2020 5:32:38 PM ******/

    SET ANSI_NULLS ON

    GO

    SET QUOTED_IDENTIFIER OFF

    GO

    ALTER PROCEDURE [dbo].[ASI_SP_VENDOR_LOOKUP]  @temptable varchar(20),  @table varchar(20),  @db varchar(20),  @from1 varchar (254),  @from2 varchar (254),  @from3 varchar (254),  @from4 varchar (254),  @from5 varchar (254),  @from6 varchar (254),  @from7 varchar (254),  @from8 varchar (254),  @from9 varchar (254),  @where1 varchar (254),  @where2 varchar (254),  @where3 varchar (254),  @where4 varchar (254),  @where5 varchar (254),  @where6 varchar (254),  @where7 varchar (254),  @where8 varchar (254),  @where9 varchar (254) AS  exec('delete ' + @temptable +  ' insert ' + @temptable + ' SELECT ' +  @db + 'PM00200.VENDORID,' +  @db + 'PM00200.VENDNAME,' +  @db + 'PM00200.VNDCHKNM,' +  @db + 'PM00200.VENDSHNM,' +  @db + 'PM00200.VADDCDPR,' +  @db + 'PM00200.VADCDPAD,' +  @db + 'PM00200.VADCDSFR,' +  @db + 'PM00200.VADCDTRO,' +  @db + 'PM00200.VNDCLSID,' +  @db + 'PM00200.VNDCNTCT,' +  @db + 'PM00200.ADDRESS1,' +  @db + 'PM00200.ADDRESS2,' +  @db + 'PM00200.ADDRESS3,' +  @db + 'PM00200.CITY,' +  @db + 'PM00200.STATE,' +  @db + 'PM00200.ZIPCODE,' +  @db + 'PM00200.COUNTRY,' +  @db + 'PM00200.PHNUMBR1,' +  @db + 'PM00200.PHNUMBR2,' +  @db + 'PM00200.PHONE3,' +  @db + 'PM00200.FAXNUMBR,' +  @db + 'PM00200.UPSZONE,' +  @db + 'PM00200.SHIPMTHD,' +  @db + 'PM00200.TAXSCHID,' +  @db + 'PM00200.ACNMVNDR,' +  @db + 'PM00200.TXIDNMBR,' +  @db + 'PM00200.VENDSTTS,' +  @db + 'PM00200.CURNCYID,' +  @db + 'PM00200.TXRGNNUM,' +  @db + 'PM00200.PARVENID,' +  @db + 'PM00200.TRDDISCT,' +  @db + 'PM00200.TEN99TYPE,' +  @db + 'PM00200.MINORDER,' +  @db + 'PM00200.PYMTRMID,' +  @db + 'PM00200.MINPYTYP,' +  @db + 'PM00200.MINPYPCT,' +  @db + 'PM00200.MINPYDLR,' +  @db + 'PM00200.MXIAFVND,' +  @db + 'PM00200.MAXINDLR,' +  @db + 'PM00200.COMMENT1,' +  @db + 'PM00200.COMMENT2,' +  @db + 'PM00200.USERDEF1,' +  @db + 'PM00200.USERDEF2,' +  @db + 'PM00200.CRLMTDLR,' +  @db + 'PM00200.PYMNTPRI,' +  @db + 'PM00200.KPCALHST,' +  @db + 'PM00200.KGLDSTHS,' +  @db + 'PM00200.KPERHIST,' +  @db + 'PM00200.KPTRXHST,' +  @db + 'PM00200.HOLD,' +  @db + 'PM00200.PTCSHACF,' +  @db + 'PM00200.CREDTLMT,' +  @db + 'PM00200.WRITEOFF,' +  @db + 'PM00200.MXWOFAMT,' +  @db + 'PM00200.SBPPSDED,' +  @db + 'PM00200.PPSTAXRT,' +  @db + 'PM00200.DXVARNUM,' +  @db + 'PM00200.CRTCOMDT,' +  @db + 'PM00200.CRTEXPDT,' +  @db + 'PM00200.RTOBUTKN,' +  @db + 'PM00200.XPDTOBLG,' +  @db + 'PM00200.PRSPAYEE,' +  @db + 'PM00200.PMAPINDX,' +  @db + 'PM00200.PMCSHIDX,' +  @db + 'PM00200.PMDAVIDX,' +  @db + 'PM00200.PMDTKIDX,' +  @db + 'PM00200.PMFINIDX,' +  @db + 'PM00200.PMMSCHIX,' +  @db + 'PM00200.PMFRTIDX,' +  @db + 'PM00200.PMTAXIDX,' +  @db + 'PM00200.PMWRTIDX,' +  @db + 'PM00200.PMPRCHIX,' +  @db + 'PM00200.PMRTNGIX,' +  @db + 'PM00200.PMTDSCIX,' +  @db + 'PM00200.ACPURIDX,' +  @db + 'PM00200.PURPVIDX,' +  @db + 'PM00200.NOTEINDX,' +  @db + 'PM00200.CHEKBKID,' +  @db + 'PM00200.MODIFDT,' +  @db + 'PM00200.CREATDDT,' +  @db + 'PM00200.RATETPID,' +  @db + 'PM00200.Revalue_Vendor,' +  @db + 'PM00200.Post_Results_To,' +  @db + 'PM00200.FREEONBOARD,' +  @db + 'PM00200.GOVCRPID,' +  @db + 'PM00200.GOVINDID,' +  @db + 'PM00200.DISGRPER,' +  @db + 'PM00200.DUEGRPER,' +  @db + 'PM00200.DOCFMTID,' +  @db + 'PM00200.TaxInvRecvd,' + @db + 'PM00200.VENDDBA' +  @from1 + @from2 + @from3 + @from4 + @from5 + @from6 + @from7 + @from8 + @from9 + @where1 + @where2 + @where3 + @where4 + @where5 + @where6 + @where7 + @where8 + @where9  )    

    GO

    Thanks

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

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

#1
André Arnaud de Calavon Profile Picture

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

#2
Martin Dráb Profile Picture

Martin Dráb 429 Most Valuable Professional

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 239 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans