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

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Invalid column name 'InvoiceReceiptDate'

(0) ShareShare
ReportReport
Posted on by 281

I am receiving the following errors when attempting to access "Enter/Match Invoices" in POP.

"A get/change operation on table 'POP_ReceiptHist' failed accessing SQL data."

in "More Info" it reports:

"Number of results columns doesnt match table definition."

To cut to the chase here the zDP_POP10300 stored procedures include the column InvoiceReceiptDate while the table POP10300 does not include this column.

I see this error on a Google search in the Partner Forum from a few days ago but cannot access it to chime in.  Is this a known issue or is there resolution?

I will add that I've deleted and recreated the Purchase Receipts Work tables and procs using SQL Utilities and the PSTL Tools.

*This post is locked for comments

I have the same question (0)
  • RBDELAMATER Profile Picture
    on at
    RE: Invalid column name 'InvoiceReceiptDate'

    Relevant blog - New 'Invoice Receipt Date' field added to comply with UK Legislation - Microsoft Dynamics GP Community

  • Verified answer
    SMike Giuffre Profile Picture
    281 on at
    RE: Invalid column name 'InvoiceReceiptDate'

    Found the problem - database version issue.  The company database was the day before the upgrade - bad mix!  Apparently the new column was added with the 2017 year-end update.

  • SMike Giuffre Profile Picture
    281 on at
    RE: Invalid column name 'InvoiceReceiptDate'

    I have more testing to do but I didn't realize that at this iteration deleting and recreating the work table in SQL Maintenance apparently fixed the problem in work, but the problem remained in history, as the error above indicates.  I recreated the history table using PSTL trying to save the data and the data was lost (warning to those who try!) but the InvoiceReceiptDate column was added.  Interestingly using PSTL to recreate and save the work table saved the data but did not fix the problem. Go figure.

    Furthermore production already has the missing column.  So the mystery deepens as this is a recent restore of prod.  I will update as I continue research.

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…

Mansi Soni – Community Spotlight

We are honored to recognize Mansi Soni as our August 2025 Community…

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Community Member Profile Picture

Community Member 2

#1
babubaskaran@outlook.com Profile Picture

babubaskaran@outloo... 2

#1
Yng Lih Profile Picture

Yng Lih 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans