Discuss, learn, ask, suggest, share all things MDM and RDM π
Recently active
Letβs say I have a table that has 500,000 rows.I need to query this table using REST API (because I want to get both published records and records still in edited/waiting for publish states).I have some params to filter the data with, but even with params, the result set could be say, 10000.I tried using the REST API using JSON call step in a plan, setting βcountβ to 10000, and the API says maximum is 1000.I see that the REST API provides the offset param as well. Is there an example of how I can use that offset param to paginate and query all the records that I will need, but in one plan/component?This component will be a part of a complex set of components as a larger operation, and Iβd prefer to not have to create an extra .ewf and iterator for it, otherwise this whole thing gets too complicate for anyone else to understandβ¦Β Any ideas?
Steps overview:Download all components Install ONE Desktop Launch ONE Desktop and create the MDM CDI example project Place the files in the right structure Modify a bunch of files so they are working on MacOS Configure the Mac permissions to run things Launch ONE Desktop and create the MDM Banking example project Launch it all (keycloak, postrgres, mdm-server, server), one by oneDownload:Builds (Latest versions here): MDM:Β Mdm-assembly-14.5.0-linux.zip ONE Desktop:Β Ataccama-one-desktop-14.5.0-macos.dmgΒ ONE MDM Server: Mdm-server-assembly-14.5.0-linux.zipΒ Β Plugins (Latest versionsΒ here, the official Postgres version for Linux missing for now): Postgres:Β Β https://drive.google.com/file/d/1Lho_9BQh78xRWR2QHAAGoQuERof-Rn-e/view?usp=sharingΒ Keycloak:Β https://ataccama.s3.amazonaws.com/products/releases/keycloak/keycloak-21.1.2-3-demo.zip Your license (.plf file)Install ONE Desktop:Install ONEΒ Desktop (Ataccama-one-desktop-14.5.0-macos.dmg) Rename the application so that there
Need help with graphQL query. I need to bring in All the metrics like DQ scores, Overall quality for CIs that are part of monitoring projects. Is there a way to get it? Also, do we have document which tells us more about when to use edges and nodes appropriately.
Hello,Is it possible to self-join tables in RDM to populate some information? I would like to try something like shown in the screenshot. Attribute 4 and 5 values are selected from RDM UI. So, dropdown should only show values from the same table where att2 = CAT2 for Att4 and att2 = CAT3Β for Att4Table1 Β Β Β Β Β Β Β Β Selection from RDM UI Β Att1 Att2Β Att3 Att4 (where att2 = CAT2) Att5 (where att2 = CAT3) Β ID1 CAT1 val1 ID3 ID5 Β ID2 CAT1 val2 ID4 ID6 Β ID3 CAT2 val3 Β Β Β ID4 CAT2 val4 Β Β Β ID5 CAT3 val5 Β Β Β ID6 CAT3 val6 Β Β Β Β Β Β Β Β Β Β I somehow tried to create self join in relationship like below. I was able toi upload configuration successfully on RDM with these relationships.Β Β However, when edit the record on RDM the lookup is blank. it does not show any value although table is populated.Β Β (this can also be understood as employee infoΒ vsΒ manager info relationship.
We have multiple Realm roles created for our data domains in the below fashionData Domain 1 Realm Role - Data Owner Realm Role - Data Steward Data Domain 2 Realm Role - Data Owner Realm Role - Data Steward How can IΒ merge Data Domain 1 and Data Domain 2 into one single New Domain and merge the corresponding Realm Roles?I.e.Data Domain 1 Realm Role - Data Owner Realm Role - Data StewardΒ Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β = New Data Domain Data Domain 2Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β New Realm Role - Data Owner Realm Role - Data OwnerΒ Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β Β New Realm Role - Data Steward Realm Role - Data Steward
How can we retrieve or read the workflow status (running, success, or failed. Etc) using a GET API after triggering the workflow via an Http service?
Hello,Β I wantedΒ to know that how do we implement matching options in the master layer of the MDMΒ project.I have used in the columns in the instance layer and then used the sameΒ in the master layer in the matching step just as used in the cdi example. and then I have used the same name in the matching step but still Β nothing is Β showing the UI part. Can someone help me with that.
Hello everyone,My organization will soon be upgrading to a higher version of Ataccama, and I want to make sure the transition goes as smoothly as possible.Β I'm reaching out to ask:What should I be documenting or looking out for before, during, and after the upgrade?Some specific things I'm wondering: Are there key areas (like DQ rules, workflows, configurations, etc.) that I should definitely back up or document? What kind of testing should I plan for in UAT? Should I be validating things both before and after the upgrade? Are there any common issues or changes I should be aware of that might affect how things work in the new version? If anyone has experience with a recent version upgrade, Iβd love to hear what worked well for youβor what you wish you had done differently!Also, if there are any official resources or checklists from Ataccama that you found useful, feel free to share.Thanks in advance!
07.05.2025 16:24:30 [INFO] Β Β Using Ataccama DQC configuration file D:\ataccama\workspace1\General MDM project - CDI example\Files\engine\trans\address\address_match.comp07.05.2025 16:24:30 [INFO] Β Β Using runtime configuration file C:\Users\AS001086183\AppData\Local\Temp\runtimeCfg31836356917877677.tmp07.05.2025 16:24:30 [INFO] Β Β Ataccama DQC engine initialized.07.05.2025 16:24:30 [INFO] Β Β Creating runtime...07.05.2025 16:24:31 [INFO] Β Β [Address deduplication] parallel processing of partitions: false07.05.2025 16:24:31 [INFO] Β Β [Address deduplication] parallel processing of key rules: false07.05.2025 16:24:31 [INFO] Β Β [Address deduplication] parallel processing of matching rules: false07.05.2025 16:24:31 [INFO] Β Β Starting runtime...07.05.2025 16:24:31 [INFO] Β Β Running runtime...07.05.2025 16:24:31 [FATAL] Β Β Internal error occurred during run of the plan: Persistence is not set (the standalone mode may not be configured)[STEP Address deduplication[Md Unify]]07.05.2025 16:
Hi everyone,In the last post of our RDM best practice series, we will go through an example Project configuration, uncovering the key nodes and functionalities. Iβll be linking further reads if you are interested in a deep dive and try testing your skills β‘Β 1. RDM Logical ModeAt the heart of the RDM model project lies the RDM Logical Model. This node is the epicenter for configuring reference data, its entities, relationships, and organizational structures. With support for a myriad of tables and relationships, you can effortlessly model data, define attributes, and establish complex hierarchies. Dive into the details at Creating the RDM Data Model.Β Β 2. Connected SystemsIn the realm of Connected Systems, databases and servers take center stage. Efficiently import/export data to/from RDM by configuring connections to external databases and remote servers. Explore detailed instructions at Adding Databases Synchronized with RDM and Adding Remote Servers for File Transfers.Β 3. Workflow Con
Hello everyone,Iβm working on a project that integrates a data masking tool with Ataccama, and Iβm encountering some issues when trying to retrieve actual catalog item data (the row-level data) via the REST API. Iβve been testing both GraphQL and REST approaches, and hereβs what Iβve found so far:GraphQL vs. REST for Data Retrieval:The GraphQL API appears to focus on metadata β attributes, versioning, policies, etc. However, based on my understanding, the actual table data (the rows and cells) isnβt available through GraphQL; itβs only accessible via a REST endpoint. Based on available documentation for MDM and RDM REST APIs, the REST endpoints follow a pattern using a fixed base path (/api/rest) on the default port (8051) and use basic HTTP authentication.Endpoint URL Confusion:Initially, I attempted to use an endpoint like:ββhttps://teranet.test.ataccama.online/catalog/data/catalogItem/<gid>/datawhich returned a 404 error. Later, based on the docs, I switched to the documented
Hi everyone πΒ Following up on our first post about getting started with Data Quality & Catalog, weβre excited to guide you through another key path in your learning journeyβMaster Data Management (MDM) and Reference Data Management (RDM).Β Whether youβre a business user, technical implementer, or solution architect, the MDM & RDM On-Demand Learning Path in Ataccama Academy will give you the essential skills to design, configure, and operate these critical components of the Ataccama platform.Β πStart with the basics to get familiar with MDM & RDM:Managing Master DataGain a foundational understanding of Ataccamaβs MDM capabilities, platform UI, and core data concepts.Managing Reference DataExplore how reference data is governed and maintained in Ataccama to ensure consistency and control.Β π§±Build on your foundation with practical configuration, workflows, and deeper implementation techniques:ONE Desktop CoreLearn to design data flows, transformations, and rules using the ONE
Β I am trying to doΒ validation on Tin , on which score and explanation are getting populated but the recordsΒ whichΒ are invalid areΒ not getting highlighted in red andΒ i have enabled validation in the Tin columnAttaching the snapshots of the steps which i have done while configuring the validation:Β Β How shouldΒ i fix this.
We made changes into the clean operation of an entity. it will take effects for new transactions.How can we apply this to the current records that we already have into the database?Β We are exploring use a full reprocess of this entity:but we have some doubts about the setup. For example:What is the difference between a reprocess vs rematch checkbox?Β We tried to read the documentation but there is not detail explanation about it.Β Thanks in advance!
I have been trying to explore the Reprocess and Rematch options in MDM.From this post I understand that Reprocess is used to reprocess the records. For example, lets say, after an initial load where the email values were not being modified in contact_clean.comp, we are now to determine which emails have the domain company-name.com and are now being updated to have domain companyname.com .Β So, I need to run the reprocess job.Rematch is to run the match step on top of the reprocess since the email values have been modified. What I do not understand is do I run a rematch job only if the email value participates in determining the master record or do I need to run it whenever the reprocess jobs is run irrespective of the changes that took place due to a reprocess?There is another question I have. When we run a load job, the change detection is done right. Does this change detection run on all the records or just the delta records. Post the change detection, matching and merging is run only
Hello all,Iβm using the Ataccama v14.5 there we have created the custom entity for classifications and created the classification types (Internal, Public etc) and added them with tables and attributes through theΒ One Desktop plan. But when i am using the same plan to deleteΒ it from table or attributes just by changing the One Metadata Writer property in GeneralΒ tabΒ βworkflow state asΒ deletedβ and in the Columns tab providing the βId Column Name as table_idβΒ then it is not deleting anything. Any guidance or suggestions is really helpful. Thanks.General tab Screenshot:Columns tab screenshot:Β
I have MDM setup and records are loaded using a Full Laod configuration. I need to create a load such that all the records that were added into the sourceΒ are moved into to MDM hub on a daily basis. The approach being used is to identify all the records updated today and load them into MDM. Can you please suggest if I needΒ to create a Delta Load for this or Full Load works. Also, I need to schedule a run ofΒ the load file on daily basis.How can I do it?
The Workflow task Run MDM Export does not recognize the export component and and gives error message.I am assuming it is because there is no path variable set for the Export folder.Can someone please help me identify the issue?
I have a workflow with a file iterator step. It runs without any issues in the IDE on my local machine, but whenever I deploy it my companyβs RDM server, I get the following error:2025-01-07 09:05:31 INFO: starting...2025-01-07 09:05:31 ERROR: Problem during initialization of iterator valuejava.io.IOException: An unexpected network error occurredΒ Β at java.io.WinNTFileSystem.canonicalize0(Native Method)Β Β at java.io.WinNTFileSystem.canonicalize(Unknown Source)Β Β at java.io.File.getCanonicalPath(Unknown Source)Β Β at com.ataccama.dqc.resources.local.FileResource.getCanonicalPath(FileResource.java:40)Β Β at com.ataccama.dqc.resources.impl.DelegatingResourceBase.getCanonicalPath(DelegatingResourceBase.java:41)Β Β at com.ataccama.adt.task.iterators.FileIterator$FileIteratorInstance.iterate(FileIterator.java:133)Β Β at com.ataccama.adt.task.iterators.TaskIteratorInstance.initAndIterate(TaskIteratorInstance.java:36)Β Β at com.ataccama.adt.task.exec.EwfForEachTaskInstance.run(EwfForEachTas
Hi everyone!Β Iβm back with the second and last part of the GraphQL best practice series. First part was all aboutΒ authentication types & which one you should use and how to authenticate GraphQLΒ requests. This post will focus onΒ how to work with MMM in GraphQL - so letβs get into it.If youβd like to check out the first part Iβm sharing it here πΒ ONE Metadata Readers Or GraphQL?Β MMM is the name for the linked list that holds all metadata and the connections between them. Pretty much everything in MMM can be explored via GraphQL - as GraphQL is what happens behind the scenes in most steps/actions in ONE Desktop.As far as ONE Desktop is concerned, while ONE Metadata Readers are often all you need, highly nested queries and associated joins can become quite tricky to handle via ONE Desktop plans, and can sometimes be simpler to build by just running a specific GraphQL query. In addition to that,Β some things, such as raw profiling information can only be extracted via GraphQL.Β Exploring
IΒ have a full load already configured for a source system. This load component has 3 different entities(party, contact, address).I have used this to load data into mdm-hub as well.However, now we want to use a different source table for party entity and want to load only the records for party entity. I am planning on using a new full loadΒ with mappings only for the party entity. Will thiscreate new instance party records and make the old records inactive? bring any change to the records for contact and address entities?Β
Security Assertion Markup Language (SAML) allows users to use one set of credentials to log into many different websites. It is an open standard that allows identity providers (IdP) to pass authorization credentials to service providers(SP).Β SAML transactions use Extensible Markup Language (XML) for standardized communications between the identity provider and service providers. SAML is the link between the authentication of a userβs identity and the authorization to use a service.Β Items to consider prior to connecting to SAML- Best PracticeIt is important to understand how your organizationβs Active Directory is setup. Some pre-requisites needed can include things such as:Do you have a list of groups you need to import? If the answer is no, you may want to speak to your engagement manager from Ataccama to discuss in detail. In short, with AD Groups we can map Ataccama Roles to a single group. This benefit of doing this is, your internal dev-ops team wonβt have to manually add/remove u
Our Incremental load operation is taking huge time (2 hrs to process 5-7K records). We have applied all performance tuning things which is there in document. Apart from this we thought of loading data from DW to PostgreSQL (MDM DB) stage table and then will use that stage table as a source in Incremental load. Idea is when the server will be same for both source and target the computation will be faster.But this direct load job is failing with below error. Kindly help on fixing this. Or please recommend on any other approach.com.ataccama.nme.core.NmeExecutionException: Plan "C:\Users\EYKU4F\Ataccama\workspace\OmniChannelMDM_Latest\Files\engine\load\EPRISM_stg_eprism.comp" execution failed: runtime.error.jdbc_reader_error - nullcom.ataccama.dqc.model.environment.AbortedExecutionException at com.ataccama.dqc.model.elements.data.flow.RecordQueue.putBatch(RecordQueue.java:173) at com.ataccama.dqc.model.elements.data.flow.RecordQueue.access$100(RecordQueue.java:35) at com.ataccama.dqc.model
Hi community πΒ Every now and then, we hear from our users wondering if itβs possible to spice up their Master Data Management (MDM) interface with something a little more visual.Recently, I worked with one of our members who wanted to mark one of the records in a group as having a special meaning, so that it would instantly stand out to data stewards. While the logic behind selecting this record was complex, the outcome boiled down to a simple boolean flag, like cmo_preferred_flag = {true | false}. However, displaying such an attribute on the screen isnβt exactly thrilling:In earlier versions, it was possible to load an image file to represent things like this, but it required customization that was tricky to maintain. Plus, it often got wiped out when regenerating the MDM project. In our current versions (14.5.x / 15.x), weβve moved to SpringBoot, and for security reasons, loading external static content is no longer supported.So, can we solve this in a fun and practical way?The emoj
HiΒ Β We are noticing behaviour in our model where a source system will split from its golden id group when updated on matching criteria fields ( in this example address). However it only does this when the group of records was manually merged onto the golden id. It wont βjump shipβ and form a new golden id when the records previously auto merged based on the matched criteria we assigned in the model.Is there a way we can stop this splitting from happening when the source system is updated?Β For example we can see here the new golden id created with one SF recordΒ Β the previous group the SF record belonged to, shows a lot of manual merging in the Match Rule Name columnΒ Our rematch if changed section shows these fields are used for rematching:Β Β We want to keep rematching switched on, to bring other source systems into the group if they meet criteria, but we dont updates on the SF record itself to allow it to break out of the group. (We dont want βauto-splitsβ)Β thanks
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.