Hi @AeJay 

Thanks for reaching out to the Community!

Thank you for explaining the situation clearly. It looks like this is something possible with Xero. However, I want to make sure that I’m providing you with the correct information.

Could you kindly send screenshoots of how you have set up the Zap so far? Please make sure to include all the fields. This would allow me to check further.

(If there’s any personal information, kindly blur them.)

Looking forward to your response! 

Hi there,

I think that these three screenshots are the most relevant (in a very long zap). Let me know if you need anything else and thanks in advance.

AJ.

Hi Cherie,

I’ve added the screen shots. Thanks.

Hi @AeJay!

Can I check that I’ve understood the issue correctly? 

When the item has a fixed unit price, the Zap works as intended. When the item has a customizable unit price, even though the unit price is added in the Xero fields (in the place indicated in the screenshot below), the action doesn’t respect this price and uses the standard one, which is $0. 

Have I got that right?

If you don’t include the item code, will that cause an issue for things on the Xero side? I’m wondering if you could leave the item code and fill in the other fields as I think that that will then use the unit price that you put into the Zap field. 

​I hope that's clear, please let us know if you have any questions!

Hi @AeJay!

Can I check that I’ve understood the issue correctly? 

When the item has a fixed unit price, the Zap works as intended. When the item has a customizable unit price, even though the unit price is added in the Xero fields (in the place indicated in the screenshot below), the action doesn’t respect this price and uses the standard one, which is $0. 

Have I got that right? Yes - Correct

 

If you don’t include the item code, will that cause an issue for things on the Xero side? I’m wondering if you could leave the item code and fill in the other fields as I think that that will then use the unit price that you put into the Zap field. 

​I hope that's clear, please let us know if you have any questions!

I think for 50% of the 10% this would work. For context, all these workflows are triggered by completion of 1 of 20 odd customized client quote forms. In the form the client selects from a description dropdown and enters quantities & processes for each line item. The are three instances where price can vary from that stored in Xero:

1. Where ‘add on’ processes are selected from a line item Smartsheet calculates a premium above base price.
2. On each form there is an option to “manually enter description”  (these are all assigned to the same item code). When this option is selected the client can type in description, price and quantity.
3. There are a few instances where price varies within a unique item code, like “fitting” or “bolts” something like that, where a unit price dropdown can appear in the form.  

I think that for item 2 above your suggestion could work, but for the others it would need to have the item code. The client still uses Xero for key reporting and we’d want it to be accurate.

Does anyone know anyway to make the Zap respect the price data provided? 

Hey there, @AeJay! Thanks for the extra context!

Full transparency, this is quite a beast of a zap you’ve built (it’s super impressive!) and this level of customization is a bit beyond the Zapier scope of what we can support. It’s possible there’s someone in the community that may have some ideas - we really do have some great minds here! 🧠 If you’re looking for a more immediate solution, you can also look into hiring a Zapier Expert to take this on for you though.

Hopefully you’ll keep us posted on your wins if you’re able to get this figured out on your own!

Hi Christina,

I’m NOT customizing anything in Zapier, I’m simply mapping Smartsheet fields to Xero fields exactly as intended. 

There doesn’t seem to be a slew of ‘experts’ here offering actual solutions. If someone comes on here and says the can resolve the issue I’d consider that. to date - crickets.

But as it stands, the Zap is mapped as intended by Zapier and isn’t functioning. I’m also considering other integration tools that will actually work and actually have customer support.

Cheers,

AJ

I’m sorry for your frustration with this @AeJay. I would expect that adding the price in Xero should overwrite the existing price for a product code too. 

There is one thing that could be causing the issue, though it’s a bit of a long shot. On the Xero API that the UnitAmount (assuming that's the Unit Price) will be rounded to two decimal places, so maybe it's expecting the prices to be supplied as 1.00, 2.00, 3.00... instead of 1,2,3...? It’s possible that there's a validation rule on Xero's side where if the price isn’t in correct format, it'll use the default value for the product. Could you try using an amount with two decimal places to see if that works? I’d recommend manually typing in some data into the Zap action to test it, rather than changing everything, in case it doesn’t work. 

If that doesn’t solve the problem, you can reach out to the support team to let them that this is a bug. You can reach out to the Zapier support team if you are on a Zapier trial, a paid plan or to report a bug. 

I’m sorry that this has been a frustrating experience for you and I hope that this gets you closer to a resolution. 

Thanks. 

Hi @Danvers,

Thanks for providing some ideas and possible solutions rather than just fobbing me off on some non-existent “Expert” who judging by this thread will know less than me:). I tried removing the item code from SS, as you suggested, which worked! This solves 50% of the problem.

Your idea of adding a .00 to currencies is a good idea, but I presume it doesn’t work - I’ve run some item codes @ $5.55 for example and they also populate as zeros in Xero. 

I’ve come up with an alternative in SS, there are usually only 4 possible prices on an item code, so I realized I could just add a suffix to each item code using a formula in SS and add more item codes to Xero i.e. “Item code-suffix.

Thanks again. I still have item 3 above to resolve… but this only affects 4 item codes, I might try and get the client to lump these in with ‘manually enter description’ items.