Announcements
I've got a new addition for a few reports that require three new fields on the header table/dataset. I've added the fields, added the logic to fill them and then opened Visual Studio to edit the report.
I selected the header dataset and issued the refresh command and after a bit the new fields are there. The problem is, in the process Visual Studio broke all the custom parameters on the report.
In addition to DocumentTitle I now also have parmDocumentTitle. In addition to RecordId I now also have parmRecordId. salesQuotationEditLinesRecId is joined by parmSalesQuotationEditLinesRecId and SalesQuotationDS_parmPrintCI is duplicated into SalesQuotationHeaderDS_parmPrintCI.
WTF? But anyway I could deal with that. Just switch the design over to the new ones right? right?
Well, not quite... Because when I export the report from our DEV system and import it into our TEST system it gets even weirder. The TEST system continues to use the OLD parameters for everything but "parmPrintCI". Somehow that's peachy.
I'm beyond frustrated and can't find a solution to fix and (in the future) prevent this mess?
Hi,
Your scenario is quite complex to be able to answer it on communities. Would you please open a support request so the Microsoft support can investigate it?
Thanks in advance
André Arnaud de Cal...
294,095
Super User 2025 Season 1
Martin Dráb
232,866
Most Valuable Professional
nmaenpaa
101,158
Moderator