Enterprise Data Management Deep Dive - Part II:  Exploring the Understated Features of EDM

Published April 21 2020 by Kevin Black
Back to insights

Introduction

Welcome to a new blog series focused on recent – and perhaps overlooked and less understood - features and enhancements in Oracle Enterprise Data Management (EDM). The objective is to clarify and highlight the subtle, but powerful, features now available in EDM.

The previous post focused on the EDM search engine. For this entry, I’d like to focus on the Import function, along with a blurb on the Inspector window in EDM.

Import

From the initial release, EDM provided two import options: Replace and Reset. Recently, a third option was introduced: Merge. All three are important yet, offer distinctive features and differences that are important to understand.

  • Replace
    • This is the most common import option I have used in my projects, and it performs what you would expect – the hierarchy relationships are replaced by the contents of the import source. This means, in terms of hierarchy relationships, an “Add” or “Delete” may occur (any hierarchy relationships in EDM that are not included in the import source will be sent to the great Node Recycle Bin in the Sky). So, it’s important to confirm your import source contains the full and complete hierarchy before importing, otherwise you will find items like alternate hierarchies may be deleted from EDM.
    • For properties, relationship-level properties are handled a bit differently. If the relationship property exists in the import source, it will overwrite what is in EDM. Otherwise, what is in EDM is retained.
  • Reset
    • Think of this as a “deep replace”. All nodes and relationships are cleared and rebuilt.
    • Hint: This is also one way to eliminate those pesky orphan nodes!
  • Merge
    • We are using this newest option in current projects, and it certainly opens more possibilities in the future. The biggest difference is that an Import-Merge will trigger (wait for it)… a Request!
    • So, what happens when the Import-Merge is executed?
      • A request is created, and if the request has no validation issues, it is auto-submitted.
      • Approval policies are bypassed.
      • EDM will add and update nodes and properties.
      • If shared nodes are enabled, EDM will perform an “insert” for nodes with a different parent. Otherwise, EDM will perform a “move”. Check those hierarchy sets, folks!
      • And guess what? Any subscriptions linked to that source viewpoint will then be triggered, so you can now enable an end-to-end maintenance process: Import ➡️ Request ➡️ Subscription Requests.
    • Be careful, however – when I first experimented with this option, I was expecting EDM to only perform add/move/update operations. But that is not the case. This option will remove nodes from EDM if they are not in the import source! Think of Import-Merge like the DRM Blend, but without the option to disable node removals.
    • Here is an example of the submitted request, generated from Import-Merge. Note the Request ID and Request Description indicate it was generated from an Import. If you Inspect the request, you will not find a request file attachment, but you will see the full details and history like any other request.

Minimize and Restore Inspector Windows

The 20.02 release was jam-packed with all kinds of goodness, including copy/model after nodes, change parent for invalid request item using drag-and-drop, node name transformations, and many others. This item snuck into 20.02 as well: “Minimize and Restore Inspector Windows”.

To be honest, I couldn’t figure out at first how the heck to do this! But as my wife likes to point out, sometimes the thing I’m looking for is right in front of me and ready to jump out and bite me. I was looking in the corners for some type of minimize/maximize symbol. The sneaky little feature is along the top edge of the Inspector window, smack dab in the middle, and only appears when you hover your mouse over it.

Summary

That concludes this blog post, and I hope it was helpful to understand the more subtle details of the EDM Import feature, along with how to find the sneaky minimize/restore option on Inspector windows. I’d love to hear any comments, questions, and suggestions, so please reach out. And check back soon for the next installment in the EDM Deep Dive series!

For comments, questions, or suggestions for future topics, please reach out to us at infosolutions@alithya.com.  Visit our blog regularly for new posts about Cloud updates and other Oracle Cloud Services such as Planning and Budgeting, Financial Consolidation, Account Reconciliation, and Enterprise Data Management.  Follow Alithya on social media for the latest information about EPM, ERP, and Analytics solutions to meet your business needs.

Contact us