The new preference, Include select statement in views reports, for reporting in Data Modeler 4.2EA includes the SQL statement used for the query to the report.

To generate a report on views select Table Views report template:

If the preference has not been set the report would look something like this:

And if it has been set it might look something like this:

The report will show the SQL statement for the view in the new Select Statement field in a report template for Table Views.

In Data Modeler 4.2EA there are some new preferences for reporting. Let’s first see the new preference Generate HTML report TOC in separate file.

This preference ONLY affects reports generated in HTML format.

This does not affect the generated report itself: it looks the same does not matter if you chose this preference or not. But it does affect to the files generated for the report. In our example a report generated without this preference only has one file: in our example AllTablesDetails_NoSeparateTOC.html. Whereas the report with this preference on has three files: AllTablesDetails_SeparateTOC.html, AllTablesDetails_SeparateTOC_index.html and AllTablesDetails_SeparateTOC_toc.html.

Note that whenever we generate a report with Data Modeler (no matter how we chose the preferences) also a file report_data.xml is generated.

Why would I like to get the TOC in separate file? While the TOC is in separate file I can for example browse the report without the TOC or print the report.

Starting in version 4.2.0 (build 917) known as 4.2EA there are new preferences for reporting that allow you to generate even better Standard template reports.

The Preferences before this release were:

And since 4.2EA:

There are five new preferences that will make your reports look and work even better than before. I will explain these Preferences in detail on my next blog posts  🙂 Stay tuned  😀

Starting in version 4.2.0 (build 917) known as 4.2EA you can define the query for a view without using the Query Builder. You can simply type or copy/paste the SQL query wanted to the new Query box in a new Query tab located in the View Properties:

You can test the query by pressing the Test Query button. If I had pressed that button I had noticed that I made a typo on table name (load vs. loan)  😀 This button is very useful…

Of course the Query Builder is also available if you rather use that. But when and why would I like to use this new functionality? I know that using this functionality there will be no lost of formatting, no problems with hints, no problems with the comments inside the query etc. In short no editing that is not done by me  🙂

Enhancements in Change Requests

Starting in version 4.2.0 (build 917) known as 4.2EA you can create Change Requests in the Browser. Right-click the Change Request in the Browser and select New Change Request.

There is also a new tool for managing the Change Requests called Change Requests Administration. You can find it under the Tools menu:

And this is how the tool looks like:

Are you interested in learning more about Change Requests?

https://helifromfinland.wordpress.com/2014/10/18/handling-change-requests-with-data-modeler/

4.2EA is mostly bug fixes but there are also some new features that I think you should know about. I will blog about some of them in a serie of What’s new in Data Modeler 4.2EA posts. This is the first one of that serie.

Design rules for a subview or a selected set of objects

Starting in version 4.2.0 (build 917) known as 4.2EA you can apply design rules to objects in a subview (they will not be applied to objects that do not exist in this subview). Simply right-click on the canvas of a subview and select Design Rules.

You can also select one or more objects from the canvas, right-click and select Design Rules. The rules will only apply to the selected objects.

What is a Design Rule?

https://helifromfinland.wordpress.com/2016/07/21/design-rules/

I love the Oracle OpenWorld time: interesting things happen!

Data Modeler 4.1.5 is out but so is the EA for 4.2!

Go and download:

http://www.oracle.com/technetwork/developer-tools/datamodeler/downloads/datamodeler-087275.html

What’s new in 4.1.5? Plenty of bugs fixed:

“Date: September 2016

This list contains only a selection of higher priority bugs, customer bugs and issues raised by the community on the OTN Forum since the release of version 4.1.3.

”

Let’s talk more about EA 4.2 a bit later…

Cheers,

Heli

Stop guessing and define it yourself!

Go to Preferences:

Select Environment, Log. Then select Save Logs to File and define the Log Directory.

What is the difference between Delet Object and Delete View?

If you right-click and object in a diagram there might be two options: Delete Object and Delete View. “Might” because the Delete View is only available if you have that object in more than one diagram.

Delete Object removes that object totally from the design: from this diagram and from all diagrams where it exists. The object is totally deleted from the design. If the object exists in more than one diagram, you will also see the Delete View option. That will delete the object BUT only from this diagram, not from the whole design.

Let’s see an example with an entity called Product.

This is the Logical Model:

This is a subview:

Now in the subview I select Delete View for the entity Product.

The Logical Model still has the entity Product:

But the subview does not: