Current filter:
                                You should refresh the page.
                                Support Center
                                • Hello Felipe,

                                  Before applying the suggested workaround, you should add the Clone Object module into your solution and then invoke the Model Editor and set the IsCloneable property of the BOModel | ReportData class node to True. After that, the Clone Action will appear for reports.
                                  Let me know if this helps.


                                • Felipe R Machado 10.15.2010

                                  That I already know. The problem is that the ReportData does not appear under the BOModel nodes... At least not in the platform agnostic module, which is where we actually drop the Clone Object Module.

                                  But, since we drop the Reporting Module into the platform specific modules, it explains why the ReportData node isn't there in the platform agnostic project.

                                  So, yes, this helped a lot! Let me try it out and I'll close this if that's the case (I really only searched for the ReportData node in the platform agnostic, and never thought about looking for it at the platform specific modules... silly me!)

                                1 Solution

                                Creation Date Rating Importance Sort by

                                You can consider the following solutions depending on the reporting module version you are using:

                                Reports V2 Module
                                1. If a report was created at design time in Visual Studio, consider one of the following solutions:

                                1.1. Use the Copy Predefined Report Action to clone a predefined report and then modify the copy (supported for both WinForms and ASP.NET);

                                When you create a predefined report with scripts that will possibly be modified by end-users, do not use XtraReport events directly. Instead, use the XtraReport.Scripts and/or XRControl.Scripts properties in the Report Designer, as demonstrated in the Scripting Overview topic. Otherwise, your code will not be copied to user scripts via the Copy Predefined Report Action. If you use this approach, add references to assemblies used in scripts to the XtraReport.ScriptReferences property. Assemblies used in your application will be attached to scripts automatically. If classes from such assemblies cause errors when scripts are evaluated, either use fully qualified names, or add the using (Imports in VB) directive at the beginning of the script.

                                If you happen to have a ready *.REPX definition for your report, create a new report and then use the built-in import and export commands in the WinForms or design-time report designer (unavailable for ASP.NET).

                                1.3. You can copy the corresponding files - YourReportName.cs, YourReportName.resx, YourReportName.Designer.cs. Alternatively, create a separate assembly with your reports and reference this assembly in all projects where these reports are required.

                                2. If a report was created at runtime, consider one of the following solutions:

                                2.1. Copy data rows in the ReportDataV2 table manually using your database server means;
                                2.2. Copy related ReportDataV2 persistent objects using programmatic solutions from the Should I use XPO to transfer/synchronize data between databases? and How execute "copy pre-defined reports" in XAF ReportsV2 from code? articles, e.g. the Cloner or ReportsStorage.CopyFrom APIs.
                                2.3. Add the Clone Object module in the Module or Application Designers and set the BOModel | DevExpress.Persistent.BaseImpl | ReportDataV2 | IsClonable property to True in the Model Editor to enable the Clone Object Action for Views with ReportDataV2 objects (available for XPO only):

                                With EF, you can use any native EF approach to clone the ReportDataV2 object, since it is a simple record in the database with a serialized report.

                                Reports Module (Obsolete)

                                Use the 2.1 - 2.3 solutions, but work with the ReportData table/type instead of the ReportDataV2 one. Be sure to add the ReportsModule component using the Module or Application Designers before invoking the Model Editor for customizations.



                                • Felipe R Machado 10.15.2010

                                  Worked like a BREEZE! Perfect! The last suggestion was very intelligent... Thanks a million (again).

                                • Willem de Vries 07.04.2012

                                  I love it! Especially because the DetailView for the cloned report is opened!

                                  Did not get it working for the platform-agnostic module however. Added the ReportModule to Module.cs (the design file showed the requiredfile line), but in the model nothing showed up.


                                • @Willem:
                                  I cannot replicate this problem in my tests. See the attached screenshot.
                                  If you require any further assistance with this, please create a separate ticket and attach your problematic sample project along with exact repro and screenshots.

                                If you need additional product information, write to us at or call us at +1 (818) 844-3383

                                FOLLOW US

                                DevExpress engineers feature-complete Presentation Controls, IDE Productivity Tools, Business Application Frameworks, and Reporting Systems for Visual Studio, along with high-performance HTML JS Mobile Frameworks for developers targeting iOS, Android and Windows Phone. Whether using WPF, ASP.NET, WinForms, HTML5 or Windows 10, DevExpress tools help you build and deliver your best in the shortest time possible.

                                Copyright © 1998-2017 Developer Express Inc.
                                All trademarks or registered trademarks are property of their respective owners