Data views is often combined with Optional Tables and Report Runner as part of a more comprehensive suite of reporting tools.
Data Views turns Sage 300's Optional Fields into columns for reporting.
Why use it?
Do you make use of Sage 300 Optional Fields?
- Are you struggling to incorporate Optional Fields and custom views into your reports?
- Did you know there is an easy way to create and maintain database views within Sage 300 that turn your Optional Fields into columns, simplifying report writing and making report running faster and more efficient?
What is it?
Data Views simplifies the use of Sage 300 optional fields in reports by using database views. Simplifies and speeds up the process. Use with your favorite report writer.
For example where the AR Customer table is ARCUS, the optional fields are stored in ARCUSO. If you have 6 optional fields – to report on them all in one report against the ARCUS table in Crystal Reports, you would need 6 outer joins to the ARCUSO table or 6 subreports to pick up the data.
Writing a database view to join the ARCUS and ARCUSO tables into one view, you can simplify the Crystal report by including only the view (for example EBCUS) in the Crystal Report.
- Easier to create and maintain custom reports when using Sage 300 optional fields
- Only create the view once for all report writers to use
- Simplify Crystal Reporting on Sage 300's Optional Fields
- Optional Fields become columns, so no need for Crystal sub-reports
- Speed up reporting on Optional Fields
- Store custom data views which can be dumped and loaded using Sage 300 standard Dump and Load utilities
- Developed in the Sage 300 SDK
Information Manager 2017 requires Sage 300 2017.