How many Report Options can I create for any given report?

I fielded this question just recently in the newsgroup, and have to admit, I had to dust off my old training manuals and do some inquiries in my Dexterity help file. Bottom line, this could well be a question worthy of a certification exam.

Straight to the answer: you can have up to 32,767 report options for any given report. The number comes from the size limitations imposed to the Dexterity drop-down list control.



You may be saying, "but, I was told that you can have 32, where does the number 32 come from?". 32 is the number of report options that can be assigned to any given report group. Now this limitation stood up to version 8 (see KB article 849505) and I am not sure it has changed for v9 and v10, but if you test it out and find a different value, I would love to hear from you.

Until next post!

MG.-
Mariano Gomez, MIS, MCP, MVP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com/

Comments

Unknown said…
I have found that version 9.0 has a similar limitation. Error pops on 33rd report option attempted to save, "Unable to save the option. There can be only 32 options." (I am attempting to save over 32 options for the Historical Aged Trial Balance-Receivables Management.) Do I understand that a Dexterity mod would be needed to increase this number? Thanks, Mike
September 9, 2009 at 2:38 PM
Robyn Evans said…
I just ran into this on GP2013 with a Purchasing Report. It is History - Distribution Detail. We added a new option and get this message: Unable to save the option. There can be only 32 options. Is this a bug from old versions? It has apparently been this way...
August 21, 2014 at 5:53 PM
Mariano Gomez said…
@Robyn,

I don't think it was a bug, but rather a self-imposed limitation. This is standard functionality that has been in the app since ever. See the second part of my post.

MG.-
August 22, 2014 at 7:40 AM
Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics
Read more

Cannot insert the value NULL into column 'CONTACT' error when clicking on Items List in Navigation Pane

Image
Moving on from my previous article on a similar subject - see Cannot insert the value NULL into column 'BASEUOFM' error when clicking on Items List in Navigation Pane , I recently came across this error,  Cannot insert the value NULL into column 'CONTACT' when clicking on the All Purchasing Transactions list under the Purchasing Navigation Pane option, after performing an upgrade from Microsoft Dynamics GP 9.0 to Microsoft Dynamics GP 2010 R2. All Purchasing Transactions list error - Purchasing Navigation List The name of the global temp table - in this case, tempdb.dbo.##2093338- varies in almost all cases, but the end result of the error is the same. The issue has been identified running Microsoft Dynamics GP 2010 RTM, SP1 or SP2. Upon further review, the issue is due to bad data in the Vendor ID (VENDORID) column in the Purchasing Receipt History table (POP30300). In summary, if you have a purchasing receipt with a blank vendor ID or a vendor ID that doe
Read more

#PowerApps: Numeric Up/Down control with persisted button press event using components

Image
I just recently returned from the Microsoft MVP Global Summit 2019 where I had a chance to meet some of the top minds in the Microsoft PowerApps and Flow space. This was a truly exciting moment as I have been learning from the very same MVPs I met - yes, we do learn from each other! In one of my hallway discussions, I ran into my buddy Mehdi Slaoui Adaloussi , Principal Program Manager at Microsoft, who I first met at Microsoft Build 2018. I had read Mehdi's recent article on reusable components and, in particular, that I had been playing with his version of the Numeric Up/Down Control. See 10 Reusable Components: tab control, calendar, dialog box, map control and more . I must start by saying that the components Mehdi put in place expose some very clever implementation techniques, so I highly recommend you download the msapp files and load them up in your environment and study them. The Numeric Up Down control in particular, caught my attention as it required multiple and
Read more