-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Query re: Xero tracking categories #10
Comments
So far I've gone down the path of adding anything like this in a custom extension - there are hooks to alter the invoice before it is pushed to Xero. In terms of adding it - aside from time constraints - I guess the question is - is it suitably generic? ie. I have in the past set it based on the custom field from events - but I'm guessing you want it off contributions? I guess contributions is fairly generic - but I feel like as soon as that is there someone would want the membership custom field :-) |
Hi Eileen |
hmm - I can see a case for this - or for doing it as an add-one extension - but that doesn't resolve the time constraint issue :-) |
I have just had a request for tracking categories to be added to transactions coming from Civicrm using this extension. Has any more thought been given to adding this capability to the extension? Thanks. |
@T4CDE Yes, I'm doing this. But I've got a problem with one client at the moment where the API doesn't actually seem to be doing what it says it should. You'll find the relevant APIs in this fork: https://github.com/mjwconsult/nz.co.fuzion.civixero/tree/mjw specifically mjwconsult@feec475 and mjwconsult@fec1d93 |
Xero allows the user to set up two sets of tracking categories. I'd like to be able to have these in CiviCRM as custom fields linked to contribution records, and have the CiviXero extension synch these along with everything else.
I'm guessing it won't do this out of the box.
Assuming not,
Many thanks for making this available by the way, with great documentation as well - impressive.
The text was updated successfully, but these errors were encountered: