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 :
Microsoft Dynamics GP (Archived)

Insert Error: Column Name or number of....

(0) ShareShare
ReportReport
Posted on by

Getting the following error message when trying to create a requisition in Business Portal - GP 10. BP has been working  fine for a long time.

'Insert Error: Column name or number of supplied values does not match table definition'

Any ideas?

 

 

*This post is locked for comments

I have the same question (0)
  • Richard Whaley Profile Picture
    25,195 on at

    I find that this occurs:

    1.  When the wrong version of a module, dictionary, or third party product is installed, or

     2.  There is custom development that is calling a procedure incorrectly,

    3.  A procedure is trying to update a table with the incorrect number of fields.

  • Community Member Profile Picture
    on at

    Thanks Richard,

    Problem is intermittent...so its not clearcut. Its disappeared now!! I'll check your ideas above.

    Thanks again.

    Ian.

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

    Hi Ian,

    I'm facing the exact same issue in my BP requisition management... Yesterday the purchasing dept tried to transfer a requisition into a PO in GP, and got this error message... This is the first time it ever happens since I work with the RM... Before I open a ticket with MS, I first wanted to check if somebody else caught the same issue in the past. Seems a bug to me ... Checked the records in the RM tables and all seems fine.

    Any suggestions ?

    Have a great day,

    Beat

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

    Hi Ian and Richard,

    Here's an update about this case... After tinkering a while with the items in this requisition with the purchasing department and the production, we figured out that it is somehow related with the Item Card in GP... Was not able to back test it, but two things were changed in GP and then it worked : the item was identified as 'Make or Buy' and had no default Site assigned to it.. Once it was changed to 'Buy' only and assigned a default site, it worked without a hitch...

    I tried to reproduce the error in the TEST environment, but no luck so far. Have to talk to the person that changed the Item Card to see if anything else was modified too.

    Have a Happy Christmas and a nice Holiday time.

    Beat

  • Community Member Profile Picture
    on at

    Good stuff Beat.

    Not having a default Site ID might do it alright.

    I doubt the Make/Buy flag in Manufacturing would be an issue - but you never know I suppose.

    Thanks for the update.

    HapPy Christmas to you too.

    Ian.

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 > 🔒一 Microsoft Dynamics GP (Archived)

#1
Community Member Profile Picture

Community Member 4

#2
Victoria Yudin Profile Picture

Victoria Yudin 1

#2
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans