Update deposits.json#40
Conversation
I propose pulling Classref (name and value) and Entity (name and value). These fields were included in a prior version of several of my Quickbooks integrations running on Stitch and I do not see them in the latest version. These are key fields for my internal software. If agreeable, please update as soon as possible so that these fields will flow through in Stitch. Many thanks.
|
Hi @talents10, thanks for your contribution! In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. |
|
You did it @talents10! Thank you for signing the Singer Contribution License Agreement. |
|
Ok, this has been signed. I am sort of new to this whole thing, so please make sure I used the correct syntax in the update I proposed. If my contribution is accepted, how quickly will it actually be implemented on the Stitch side? Also, if you agree with these changes, I will propose something similar for journal entries and purchases. |
|
It appears that these changes I proposed on class ref name and code and entity ref name and code were incorporated in the main branch. Can you let me know if I see that correctly and when the updates will flow through to my production Stitch tables so I can bring in these fields? Thanks |
2 participants
I propose pulling Classref (name and value) and Entity (name and value). These fields were included in a prior version of several of my Quickbooks integrations running on Stitch and I do not see them in the latest version. These are key fields for my internal software. If agreeable, please update as soon as possible so that these fields will flow through in Stitch. Many thanks.
Description of change
(write a short description or paste a link to JIRA)
Manual QA steps
Risks
Rollback steps