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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Number of results colu...
Microsoft Dynamics GP (Archived)

Number of results columns does not match table definition when the SOP Posting Journal report is executed

(0) ShareShare
ReportReport
Posted on by Maria Roa

Good morning...

The situation is the following:
The migration of a SOP Blank Invoice Form report from the MSDGP2010 version to the MSDGP2015 version was made. In the update was not made by the utilities.
The report SOP Blank Invoice Form in MSDGP2015 is executed correctly with an invoice transaction printed. However, when the transaction is to be posted, at the moment the report SOP Posting Journal is executed, it issues the following message and the posting is interrupted.

Even if the report  SOP Posting Journal is printed from the batch, it shows the error and the report SOP Posting Journal is not executed and the information it shows is at zero.


If the SOP Blank Invoice Form report is made completely in the MSDGP2015 version, the SOP Posting Journal report error does not occur.

Through the notepad, I compared both reports (SOP Blank Invoice Form of MSDGP2010 with SOP Blank Invoice Form of MSDGP2015 made directly in this version) and the difference that I found is that the SOP Blank Invoice Form report of MSDGP2010 contains the following line:

DexRowTimestamp "false"

This line is not found in the SOP Blank Invoice Form report of MSDGP2015 made directly in this version.

If the SOP Blank Invoice Form report of MSDGP2010 removed this line or modified the value false to the value true directly in the notepad, and imported the report in MSDGP2015, the SOP Posting Journal report runs correctly.

My question is this: why does the sentence influence
DexRowTimestamp "false" in the SOP Posting Journal report, if this statement is in another report (SOP Blank Invoice Form).

As we know, this statement (DexRowTimestamp "false") is not placed from Report Writer since there is no option that can be marked to place that sentence in the report. Why this statement no longer exists in the report made completely in MSDGP2015?

*This post is locked for comments

I have the same question (0)
  • David Musgrave MVP GPUG All Star Legend Moderator Profile Picture
    David Musgrave MVP ... 14,149 Most Valuable Professional on at

    Hi Maria

    The DexRowTimeStamp is a table property not a report property.  It is possible that the package you are exporting is including the table definition as you might have added additional relationships.

    When a table definition includes this property Dexterity will add a DEXROW_TS column of DateTime datatype in the table.

    Between version GP 2010 and GP 2015 the SOP_HDR_WORK and SOP_HDR_HIST tables have two added fields in the table called “Print Phone Number GB” and “Workflow Status”.

    If you imported the old table definition into GP 2015 reports dictionary, you will get incorrect number of columns errors when printing the report.

    How exactly are your upgrading the report? Are you using Dynamics Utilities to upgrade the dictionaries?  Are you just trying to export and import packages?

    I suggest asking this question on the forums and emailing me the link. That way all the community can assist.

    Kind regards

    David

  • David Musgrave MVP GPUG All Star Legend Moderator Profile Picture
    David Musgrave MVP ... 14,149 Most Valuable Professional on at

    Hi Maria

    Can you post more details?

    How did you get the files you compared in notepad?

    Can post a bit more of the contents of the file, especially the section around the DexRowTimestamp "false" part

    Is that in a table definition section?

    David

  • Maria Roa Profile Picture
    Maria Roa on at

    Hello,

    The files are the extracted reports of MSDGP2010 and MSDGP2015 and their extension is .package. Then, on the .package file I right click and open the file in the notebook, each one separately and I was comparing the lines until observing that the DexRowTimestamp statement "false" was not in the report of the version MSDGP2015 made completely in this version, but it is in the MSDGP2010 report.

    Indeed, the sentence is found in the table definition section SOP_HDR_WORK

    I send you the report of MSDGP2010 that contains the sentence seen from the notebook (I highlighted the sentence in red):

    = Table "SOP_Document_HDR_TEMP"
    {
    ~Relationships
    {
    Relationship "sopUsrDefWorkHist"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "SOP Type"
    }
    RelationshipField "00001"
    {
    Field "SOP Number"
    }
    }
    Key "1 ; sopUsrDefWorkHist_ID"
    RelatedTable "sopUsrDefWorkHist"
    RelationshipType "OneToOne"
    }
    }
    }
    = Table "SOP_HDR_WORK"
    {
    DexRowTimestamp "false"
    ~Relationships
    {
    Relationship "Batch_Headers"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Batch Source"
    }
    RelationshipField "00001"
    {
    Field "Batch Number"
    }
    }
    Key "1 ; Batch_Header_Key1"
    RelatedTable "Batch_Headers"
    RelationshipType "OneToOne"
    }
    Relationship "IV_Location_SETP"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Location Code"
    }
    }
    Key "1 ; IV_Location_SETP_Key1"
    RelatedTable "IV_Location_SETP"
    RelationshipType "OneToOne"
    }
    Relationship "MC_Currency_SETP"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Currency ID"
    }
    }
    Key "1 ; MC_Currency_SETP_Key1"
    RelatedTable "MC_Currency_SETP"
    RelationshipType "OneToOne"
    }
    Relationship "RM_Class_MSTR"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Apply Withholding"
    }
    RelationshipField "00001"
    {
    Field "Batch Source"
    }
    }
    Key "3 ; RM_Class_MSTR_Key3"
    RelatedTable "RM_Class_MSTR"
    RelationshipType "OneToOne"
    }
    Relationship "RM_Customer_MSTR"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Customer Number"
    }
    }
    Key "1 ; RM_Customer_MSTR_Key1"
    RelatedTable "RM_Customer_MSTR"
    RelationshipType "OneToOne"
    }
    Relationship "RM_OPEN"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Customer Number"
    }
    }
    Key "1 ; RM_OPEN_Key1"
    RelatedTable "RM_OPEN"
    RelationshipType "OneToMany"
    }
    Relationship "RM_Sales_Territory_MSTR"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Sales Territory"
    }
    }
    Key "1 ; RM_Sales_Territory_MSTR_Key1"
    RelatedTable "RM_Sales_Territory_MSTR"
    RelationshipType "OneToOne"
    }
    Relationship "RM_Sales_WORK"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Batch Number"
    }
    RelationshipField "00001"
    {
    Field "SOP Number"
    }
    }
    Key "5 ; RM_Sales_WORK_Key5"
    RelatedTable "RM_Sales_WORK"
    RelationshipType "OneToMany"
    }
    Relationship "RM_Salesperson_MSTR"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Salesperson ID"
    }
    }
    Key "1 ; RM_Salesperson_MSTR_Key1"
    RelatedTable "RM_Salesperson_MSTR"
    RelationshipType "OneToOne"
    }
    Relationship "SOP_Prospect_MSTR"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Customer Number"
    }
    }
    Key "1 ; SOP_Prospect_MSTR_Key1"
    RelatedTable "SOP_Prospect_MSTR"
    RelationshipType "OneToOne"
    }
    Relationship "SY_Comment_MSTR"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Comment ID"
    }
    }
    Key "1 ; Series-Comment ID"
    RelatedTable "SY_Comment_MSTR"
    RelationshipType "OneToOne"
    }
    Relationship "SY_Record_Notes_MSTR"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Note Index"
    }
    }
    Key "1 ; SY_Record_Notes_MSTR_Key_1"
    RelatedTable "SY_Record_Notes_MSTR"
    RelationshipType "OneToOne"
    }
    Relationship "SY_Shipping_Methods_MSTR"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Shipping Method"
    }
    }
    Key "1 ; SY_Shipping_Methods_MSTR_Key1"
    RelatedTable "SY_Shipping_Methods_MSTR"
    RelationshipType "OneToOne"
    }
    Relationship "TX_Detail_MSTR"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Tax Schedule ID"
    }
    }
    Key "1 ; TX_Detail_MSTR_Key1"
    RelatedTable "TX_Detail_MSTR"
    RelationshipType "OneToOne"
    }
    Relationship "TX_Schedule_MSTR"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Tax Schedule ID"
    }
    }
    Key "1 ; TX_Schedule_MSTR_Key1"
    RelatedTable "TX_Schedule_MSTR"
    RelationshipType "OneToMany"
    }
    Relationship "sopTrackingNumbersWorkHist"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "SOP Number"
    }
    RelationshipField "00001"
    {
    Field "SOP Type"
    }
    }
    Key "1 ; sopTrackingNumbersWorkHistIdx_ID"
    RelatedTable "sopTrackingNumbersWorkHist"
    RelationshipType "OneToMany"
    }
    }
    }
    = Table "SOP_LINE_WORK"
    {
    ~Relationships
    {
    Relationship "IV_Item_MSTR_VNDR"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Item Number"
    }
    }
    Key "3 ; IV_Item_MSTR_VNDR_Key3"
    RelatedTable "IV_Item_MSTR_VNDR"
    RelationshipType "OneToMany"
    }
    Relationship "IV_Price_Level_SETP"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "PriceLevel"
    }
    }
    Key "1 ; IV_Price_Level_SETP_Key1"
    RelatedTable "IV_Price_Level_SETP"
    RelationshipType "OneToOne"
    }
    Relationship "TX_Detail_MSTR"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Item Tax Schedule ID"
    }
    }
    Key "1 ; TX_Detail_MSTR_Key1"
    RelatedTable "TX_Detail_MSTR"
    RelationshipType "OneToOne"
    }
    Relationship "TX_Schedule_MSTR"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Tax Schedule ID"
    }
    }
    Key "2 ; TX_Schedule_MSTR_Key2"
    RelatedTable "TX_Schedule_MSTR"
    RelationshipType "OneToMany"
    }
    Relationship "ivItemCurr"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Item Number"
    }
    }
    Key "1 ; ivItemCurrIdxID"
    RelatedTable "ivItemCurr"
    RelationshipType "OneToMany"
    }
    }
    }
    = Table "SOP_Serial_Lot_WORK_HIST"
    {
    ~Relationships
    {
    Relationship "IV_Lot_Attributes"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "Item Number"
    }
    RelationshipField "00001"
    {
    Field "Serial/Lot Number"
    }
    }
    Key "1 ; IV_Lot_Attributes_Key1"
    RelatedTable "IV_Lot_Attributes"
    RelationshipType "OneToOne"
    }
    }
    }
    = Table "sopUsrDefWorkHist"
    {
    ~Relationships
    {
    Relationship "sopTrackingNumbersWorkHist"
    {
    Fields
    {
    RelationshipField "00000"
    {
    Field "SOP Number"
    }
    RelationshipField "00001"
    {
    Field "SOP Type"
    }
    }
    Key "1 ; sopTrackingNumbersWorkHistIdx_ID"
    RelatedTable "sopTrackingNumbersWorkHist"
    RelationshipType "OneToMany"
    }
    }
    }

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

    Hi Maria,

    This is exactly what David was asking.. You can't just upgrade your GP from 2010 to 2015 and just keep using the REPORTS.DIC as is.. You mention in your original post that

    [...] The migration of a SOP Blank Invoice Form report from the MSDGP2010 version to the MSDGP2015 version was made. In the update was not made by the utilities.[...]

    If you didn't upgrade your Report dictionary, how do you get it working in GP.. ? not upgrading the REPORTS.DIC may work with the new version, but you're likely to run into issues like the one you encountered.

    As you seem to have saved the report from GP 2010 as a .package file, did you also re-imported the .package file into your new GP 2015 under : Dynamics GP menu > Tools > Customize > Customization Status > Import ?

    Please let us know how exactly this was upgraded from 2010 to 2015.

     

  • Suggested answer
    David Musgrave MVP GPUG All Star Legend Moderator Profile Picture
    David Musgrave MVP ... 14,149 Most Valuable Professional on at

    Hi Maria

    Please delete that line and import the package.

    In GP 2015, the Dex Row Timestamp property should be true. Changing it to false will generate an incorrect number of columns error when printing reports.

    The only changes we want to make to the table definition is adding the relationships.

    I think it could be a bug that the line is even there.

    David

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Anthony Beatty Profile Picture

Anthony Beatty 2

#2
Shravan Attelli Profile Picture

Shravan Attelli 1

#2
CP04-islander Profile Picture

CP04-islander 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans