Issues Joining Transaction Details to Primary Dataset
I have two datasets. One is structured as the "primary" expense file, where each row is dates and other dimensions for each credit/debit. The next is credit card transaction details.
They share transaction IDs in a column named Doc, share GL #'s, and share posted dates. The combination of all 3 of these things will result in a unique join. My issue is this: there are other values besides transaction IDs in the Doc column in the expense file. Below is what I mean:
The orange underline are the other expenses in the source file that are not credit card transactions. But the transaction IDs are in that same column. This is my issue. How can I properly join on transaction ID so that the output of the ETL below is the entire expense file but with CC transaction details?
I tried seperating the process of the join and then appending to the expense file but that hasn't worked properly. Below is my current ETL, I am happy to elaborate on any particular part:
Best Answers
-
Feel free to schedule some time. Might be easier just to see what you're working with than back and forth messaging:
John Le
Let me make you the me of your organization for Domo
Click here for more video solutions:
0 -
Thanks for solving, had some duplicate names and unnecessary columns and John the dashboard dude helped me fix them. Thanks again!
2
Answers
-
Hi @hunter_brown ,
I tried to follow, but it's a bit hard without as much context:
Feel free to book 30 with me and I can see if I can help:
John Le
Let me make you the me of your organization for Domo
Click here for more video solutions:
0 -
Hey thanks for the quick response. Your thinking of seperating and appending is what I am doing. The 0 and 1 is no and yes for a credit card transaction. This leads me to think my way of thinking about appending is wrong.
The issue isn't with getting the details merged with the rest of the expenses so much as it is that the totals are wrong and I am trying to validate where it has gone wrong. Below is a screenshot of my join and then my append:Hope this helps give some context.
0 -
Hi @hunter_brown ,
Oh okay helps a bit more. For append, can you choose "include all columns" instead of "create transaction type (CC)" and see what that does to your numbers?
John Le
Let me make you the me of your organization for Domo
Click here for more video solutions:
0 -
So I have been validating back and forth, and it turns out that not every transaction id, GL and posted date are unique.
What is happening is that post-ETL, the transactions are summed almost as if they had been grouped, even though I don't have a group by. So in the source expense file, there will be two transactions, one for 500 and one for 15 dollars. In the ETL, there will be two transactions for 515 dollars.
This indicates to me I need more join keys to ensure it is unique, would you agree?0 -
@DashboardDude I would appreciate some more assistance on this to get to a unique key. I want to use negative line amounts from CC details to match to credits (so I would have to make credit negative), and the rest of the line amounts to line up to debits. Do you know how to tackle something like this?
0 -
Feel free to schedule some time. Might be easier just to see what you're working with than back and forth messaging:
John Le
Let me make you the me of your organization for Domo
Click here for more video solutions:
0 -
Thanks for solving, had some duplicate names and unnecessary columns and John the dashboard dude helped me fix them. Thanks again!
2
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.6K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 2.9K Transform
- 102 SQL DataFlows
- 626 Datasets
- 2.2K Magic ETL
- 3.9K Visualize
- 2.5K Charting
- 755 Beast Mode
- 61 App Studio
- 41 Variables
- 693 Automate
- 178 Apps
- 456 APIs & Domo Developer
- 49 Workflows
- 10 DomoAI
- 38 Predict
- 16 Jupyter Workspaces
- 22 R & Python Tiles
- 398 Distribute
- 115 Domo Everywhere
- 276 Scheduled Reports
- 7 Software Integrations
- 130 Manage
- 127 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 11 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 110 Community Announcements
- 4.8K Archive