Data Validation with Pigment

  • 1 December 2021
  • 0 replies
  • 433 views

Userlevel 3
Badge +6

 

This article will share some strategies and tips on how you can leverage Pigment to boost your data accuracy through best practices and data validation.

 

Table of Contents 

 

Why Data Accuracy Matters

 

Simply put, your business outputs are only as good as the source information you feed into them. Failing to use accurate data can affect beyond the limits of what's acceptable. It can impact the performance and credibility of businesses.

 

Common challenges leading to data inaccuracies include poor data architecture and poor data management practices. For many growing businesses, it can take a while until they are equipped with the tools and dedicated staff they need to ensure effective data management.

wwR5mtv7Hc0ToChofNqBTEGUniNWUhHF7iCZ-oK2vBDuOa9cgoSY0mi55j6JEILuOSxMODu4JDf686_zXKHnAkkRZmD8jbDSZ2-7NZKNDlKnkgVwB3Ko4LHs9o5y4pXzHoUHrVL2

A Note on Best Practices

 

Before we look at some product tips to help you validate data once it lands in Pigment, it's important to remember that when it comes to implementing data validation checks, the universal rule is: less is more!

 

What we mean by this is that the cost of fixing data downstream is always higher than prioritizing accuracy rules at the start.

 

Regardless of the data you are trying to load, there are two universal rules that pave the way to a robust data framework.

 

💡 Start with cleaning data at the Source

 

By eliminating the root cause of your data anomalies before they make their way to the Pigment database, you are enforcing a reliable model that is less prone to error, scalable and easy to maintain.

 

‍🔬 Follow data management best practices

 

Making the right decisions when configuring your lists in Pigment can also go a long way. A common example is choosing the appropriate unique identifiers for dimensions.

 

Here is an example of an inevitable and impactful design decision: Choosing the unique property for your dimension. In the specific use case of transaction data, a common mistake is to use an Account description as the unique property, instead of system-generated IDs by the source systems.

 

What could go wrong?

 

55uMCigoda4urawl3-Zy74KsXiOKaBVXRSMHP0rdh6WNPjwmm3Aspj2BSC0KMQxeC_3KrQmYUHGFiOCuwzn2tzK6OLTgj4AEySxm4q_1IlS33Zh1pQ7nbpBmfYrY6m4wckhZYUQ5

 

 

Top Tips for data validation with Pigment

 

Pigment allows users to bring data from various source systems such as ERPs, CRMs, and Human Capital systems and perform business logic to create reports and visualizations.

 

There may be instances where incoming data contains anomalies that need to be addressed before they form part of the valid business data.

 

In Pigment, you can easily error-proof data by incorporating data modeling best practices and leveraging a data validation workflow that allows you to audit data.

 

👩‍🔬 Create Data Quality Boards

 

Gxyms58MWjg0fO8U2VWm2AS-0FPL6sDrGnmuqeTG2KHnpg9rRUzIbQ0vKjhEmgIuAl-wdp6bMiak27a5Fi5qr_PdzIfYnE7J037rIScelPIzUbl1Ga9a_2QYP085Mhkwsk7oBE5r

 

Leverage Pigment Features to handle common use Cases

 

Handling Missing Data: 

 

fBqp6qRlhwE19bAurBXxHhlTbP2mO7bjJLklqlUhRhOQaiB8Alc7eFRy3AZoHY9E9drx4ZNcjn04mji4lu15STM2iBp-DVezFW-VTC6INF16BZ-pClh4OLSbHPe82GlyGdwlBTE9

Comment below with any tips you might have!

 


0 replies

Be the first to reply!

Reply