Has anyone successfully got a budget veriance working from XERO API? It doesn't provide it as an end point and I've been tryingt to come up with soltions to self generate it. But I'm finding bottle necks everywhere I turn.
I was thinking we could fetch all the transactions and build it again locally, but they are lacking massively as each one in the 'BankTransactions' report contains very little details, so I would then need to fetch all the details per transaction, if theres say 1,000 transactions in the last year then we use our 1/5 of our allowance and it's 60 API calls a minute so that will take forever.
Has anyone come up with a solution?
Related
So I have this problem which is bugging me for past few days.
I'm trying to make a recurring payment for X month of time with Paypal.
Recurring payment itself is working find with Billing Plan and Billing Agreement, but the problem happened in the next stage.
It needs to total up to X amount of money.
So for example, If a customer wants $100 to be paid over 3 months, it will $33.33 monthly and this will total up to $99.99, not $100!
Therefore I was trying to find something that would make me allow to change the last month payment but there was no luck.
Last thing I was going to try was making two separate payment definitions (trial and regular although they both are not trial) and set one as different amount.
Is there any better idea of implementing this feature or anything I couldn't find?
And one more question - what is the difference between trial and regular payment? I know what they mean but what's different in payment wise/program wise? Can I make regular payment definition as trial so I could just have trial payment with different $$$ and then when trial ends, proper regular payment goes through?
A trial period will work for what you propose, the only disadvantage is that the verbiage might confuse the customer during checkout, since they will see it broken down that way.
what is the difference between trial and regular payment?
The difference is that one is called 'trial' and one is called 'regular', and one happens before the other. So basically, no other important differences so long as the system accepts the parameters you're setting.
FWIW, most customers would appreciate you rounding down each period and just charging them 33.33. They would think that's fair enough.
Is it possible to anonymously programmatically verify that a transaction has reached n number of validations without running a full node? If so, what is the best means to do this?
Basically I want it to build a payment system where after the transfer is initially detected, the customer sees a message thanking them and telling them that their purchase will be processed within 24 hrs and that they'll receive an email once confirmation is complete. Then throughout the day maybe run a cron job that checks that each transaction reaches the desired number of validations and if so divide the money between two wallets and mark the product to be sent. I also don't want it to be with a service like Coinbase or Bitpay where they have control of your coins.
So far I've been experimenting with Blocktrail and mycelium gear. Both have some elements I like but still not everything that I need. With mycelium you can set the number of verifications but for instance if I want to set it for 6 verifications the customer would have to sit there possibly an hour before they see the next screen. Blocktrail allows me to query that a transaction is validated but it only has the ability to check that 1 validation was completed as far as I can tell. Can anyone suggest an API or widget that can accomplish these things? Preferably PHP or if not JQuery.
Blockchain.info has a simple Query API for querying how much bitcoin an address has received. You can add a confirmations=n parameter that will only include bitcoin that has been confirmed 'n' times. It returns a simple value in satoshis.
For example to check how much bitcoin was received with at least 2 confirmations at a specific address you could have your code query the API like this:
https://blockchain.info/q/getreceivedbyaddress/1PFtyX9nQvjP8U2N3iUk2oNorzPfpjX9sK?confirmations=2
I have more than 600k products in my shopify store . the store is taking too much time to upload a products in admin back-end ( 11k product is taken almost 8 hours to complete the upload process )
I have even Used the "shopify product API" to add my product to store .
Even API is taking to much time to insert a product to store .
Now i am in big confusion that which i prefer to upload the product .
whether through "admin back-end" or "shopigy API call .
please suggest me a best way ..
thank you
If you have that many products you should either be looking at Shopify Plus or another platform entirely.
Each product takes one API call to upload and over time your API call limit averages out to 2 per second so 600k products with one variant per product would take 83 hours to upload. Your 11k products should only take 1.5 hours to upload though so unless you have a number of apps running there is something wrong with your API setup.
If you maximize the partition of your products into variants you can upload a product and its variants in a single call. Each product may have up to 100 variants so if you can group your products into variants the theoretical saving could be down to 6k API calls and just under an hour of processing (if you have variant images I think you'd need 3 calls per product/variant/image group - 1 to upload the products/variants/images; one to read the variant and image ids; one to assign the images to the variants.
Shopify Plus has 5 times the API limit (though I can't find an official confirmation of this) so your 600k products could be uploaded in 16 hours.
As #bknights said putting all the variants and combining products as variants is the fastest way.
I'd also like to add this: split your portfolio into lots and using API you can have parallel API calls running.
I have to update 60K variants on my store once a week. As I figured out it used take an entire weekend sometimes to finish of the things. I must add that I use PowerShell for this task. Later I came to realize that while one call is running my program is running idle and by trial and error I came to a conclusion that I can have 4 call made at 250 milli seconds gap each. So I update variants of all the products (each having around 45 variants) in a single call.
This way, the time cut down to less than 1/12th of the total time. Also you can use the API call limit returned by Shopify to calculate the time gaps further. For a non-Plus Shopify account this is the fastest way possible.
Does anyone know how to use Rally Web service APIs to calculate the total amount of accepted work delivered by the last day of the iteration and the total amount of accepted work delivered since the last day of the iteration.
Thanks
You can find that information using the Lookback API. Every time an artifact changes in Rally it takes a snapshot of that data. If you query that API for artifacts that have had their Schedule state changed during those time periods you will be able to gather the information you want.
I am making changes to my companies internal paysite in order to come into compliance with the new credit card regulations. We have decided that when we get a split tender transaction that comes through we want to get the remaining balance along with how much was on the card to start out with and send that info back to the customer service rep with a message relaying the need for another payment source along with the remaining balance and the amount that was originally on the card.
Instead of chaining the transactions together with the split tender Id we have decided we would like to finalize each split tender transaction with a prior_auth_capture and then request the next payment source and amount and process that transaction in the same manner. I know that we are side stepping the functionality some but those are my orders.
My questions are, is this feasible and possible and how do you do this in code? I am using the C# SDK to implement this in VB.NET 2008
My thoughts are that I would have to process the transaction for the amount passed as a auth_capture transaction and then some how do the prior_auth_transaction with a zero amount or something?
How would this work?
Thanks for much for your help.
James
This is not feasible to do. The purpose of split tender payments is to logically group together split payments into one transaction. By breaking it up into multiple transactions it can get confusing for you, the users, and the processor. Especially if you have issues getting the user to make full payment on their transaction. Failing to void the other transactions would be very problematic. This almost certainly will result in an increased exposure to chargebacks.