Skip to main content
Question

Xero Find or Create contact error: "No property or field 'xxxx' exists in type 'Contact'

  • 19 October 2023
  • 31 replies
  • 55364 views

I’m trying to create a Zap that takes a Gravity Form (in this case a wholesale order form), and looks on Xero (my accounting software) for that contact. If it finds the contact it needs to create an invoice for the contact; if it doesn’t find the contact then it needs to create the contact and then create an invoice.

But I’m getting stuck on the Find or Create contact stage. When I test it, it says ‘No property or field 'xxxx' exists in type 'Contact' (where xxxx is the name of the contact). But I can’t work out what to do to solve this…

Can anyone help?

This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

31 replies

Userlevel 1
Badge

Ah-ha! I get it. So I put this in (see screenshot), and as Mostly Books already is in my Xero contacts, I wouldn’t expect it to create it again, and it didn’t. So I presume that works!

Userlevel 7
Badge +14

@johnmorsebrown 

Remove the mapped dynamic pill variable.

Instead select an option from the dropdown list. (e.g. Search By = Email)

The in the field below add the dynamic pill variable for the value to search by in that field.

 

Userlevel 1
Badge

I don’t quite understand - do you mean change it to something like this? (See attached)

Userlevel 7
Badge +14

@johnmorsebrown 

The Search By field is a dropdown with standardized options.

You’ll want to select an option from the dropdown list.

 

Userlevel 1
Badge

No problem - thanks for looking into it for me Troy - hugely appreciated! I’ll add the screenshots below. The first 3 are just different parts of the same page as I scroll down the form, and then the 4th is the result of the test.

Let me know what you think.

Userlevel 7
Badge +14

Hi @johnmorsebrown 

Good question.

To help us have true context, please post screenshots with how your Zap steps are configured along with the encountered error.