DECLARE @GroupId AS varchar(20)
SET @GroupId = 'FA1' --set this to your Definition Group ID
--change all 8 database names to match your environments
INSERT INTO AX42_DB_TEST.dbo.sysExpImpGroup SELECT * FROM AX42_DB_DEV.dbo.sysExpImpGroup WHERE groupId = @GroupId
INSERT INTO AX42_DB_TEST.dbo.sysExpImpTable SELECT * FROM AX42_DB_DEV.dbo.sysExpImpTable WHERE groupId = @GroupId
INSERT INTO AX42_DB_TEST.dbo.sysExpImpField SELECT * FROM AX42_DB_DEV.dbo.sysExpImpField WHERE groupId = @GroupId
INSERT INTO AX42_DB_TEST.dbo.sysExpImpTableQuery SELECT * FROM AX42_DB_DEV.dbo.sysExpImpTableQuery WHERE groupId = @GroupId
I've also read that when you use standard Data Export/Import move a definition group itself, CRs are stripped out of your conversion code. (http://gotdax.blogspot.com/2009/12/dynamics-ax-import-export-tool-digging.html) This gets around that problem as well.
Dynamics AX (D365 Finance & Operations) Implementation, Architecture, and Development
Showing posts with label SQL. Show all posts
Showing posts with label SQL. Show all posts
Thursday, January 14, 2010
SQL Query to Move Definition Groups
It's not possible to use Definition Groups (Admin,Periodic,Data Export/Import, Definition Groups) to move data held in shared tables. So, here's the quick and dirty sql query that I use (in SQL Server Management Studio) to do the job.
Thursday, December 31, 2009
Database fields in SSRS page header
Scenario
A financial report that I'm writing has columns for current year, prior year, etc. The dates that define the columns are calculated based on the users entry of a report parameter date. (i.e. current year start = January 1st of the year of the report parameter date). These dates were declared and calculated in a dataset query and then used as parameters in the TSQL query. This worked fine. I ran into some trouble when I wanted to display the calculated dates in the header of the report. We're using SQL Server 2005 and Visual Studio 2005.
What DID work
1. Create a dataset to calculate the dates based on the report parameters. Select the calculated values into a table.
2. Create an internal report parameter for each calculated date and set the available values and default value based on the dataset above.
3. These internal report parameters can be used in other dataset queries and in the report header.
What I could have done but didn't want to
What I could have done but didn't want to
A financial report that I'm writing has columns for current year, prior year, etc. The dates that define the columns are calculated based on the users entry of a report parameter date. (i.e. current year start = January 1st of the year of the report parameter date). These dates were declared and calculated in a dataset query and then used as parameters in the TSQL query. This worked fine. I ran into some trouble when I wanted to display the calculated dates in the header of the report. We're using SQL Server 2005 and Visual Studio 2005.
What DID work
1. Create a dataset to calculate the dates based on the report parameters. Select the calculated values into a table.
What I could have done but didn't want to
What I could have done but didn't want to
- I could have rewritten the TSQL that calculated the dates in an expression within the report...but didn't want duplicate code.
- The date variables that I declared in TSQL were not accessible to the report fields
- I tried declaring internal and/or hidden report parameters and setting their values in TSQL. I couldn't find a combination of settings that allowed me to set the value of the report parameters
- I tried creating a second dataset that calculated my dates and returned them as a single-row. This seemed promising, but for some reason SSRS restricts referencing fields in the report header. That's a strange one. I read several articles indicating that you can get around this issue by putting a hidden field in the body of the report...and then doing 4 other goofy workarounds to make it consistently available on multi-page reports...yuk.
Subscribe to:
Posts (Atom)