Open apwidejulien opened 2 weeks ago
@nhan-nguyen-se any thoughts on this?
The questions are about business logic which I have very little with this app. @apwidejulien Do we have a deduplication logic already? If so I think we can extend it to handle more duplication cases we found here.
You probably have more knowledge about business logic with this app than me :smile:
To unblock the import, I ended with this crappy stuff: https://github.com/apwide/marketing-automation/commit/fd1ca73a8d56f10414466751aad73ac5ec84c3cd
If I understood correctly, except for refund, we make a hard assumption that we should have only 1 pair transactionId-licenseId which result in 1 deal into HubSpot.
However, with our example, we can see this case can happen. I have the feeling Atlassian recently changed the cardinality of the transactions export to not returning transaction, but transaction lines... (a new column appeared in the mkp export named transactionLineItemId
)
What I did was just suffixing the transactionId
with transactionLineItemId
for the duplicates after having sorted them by maintenance date, so deals should be created for each transactionId
, but the problem should probably be fixed in the core to map deal using pair license/txId/txLineId.
Hmm ok I think that makes sense @apwidejulien Any chance you can help with the core changes?
It seems a new "pattern" appeared recently in our marketplace reporting; several entries with same order id (transaction id):![image](https://github.com/Atlas-Authority/marketing-automation/assets/51111685/ffc55e55-0820-43d4-b763-e0e54d0df9ee)
For the provided example, we have:
This result raise an error in action generation:
I would be more than happy to help with, but not sure how to deal with this:
Thanks in advance for your help!