Hi @juanalonsomelero 

For us to have more info, post these screenshots:

• how your Zap step is configured in EDIT mode so we can see the field types
• the encountered error

Hi @Troy Tessalone attach de images: 

 

@juanalonsomelero 

No images were attached.

Sorry, @Troy Tessalone don’t know what happened. 

@juanalonsomelero 

Error indicates an Organization or a Person must be provided.

Hi @Troy Tessalone thanks for your answer. Stills giving me problems: 

@juanalonsomelero 

Error indicates an issue with a custom field.

We would need to see screenshots showing all the fields and how they are mapped from the Pipedrive Create Lead step.

Hi @juanalonsomelero 

Were you since able to get those “provided dataset is not valid Custom field validation failed” errors resolved?

If so, would you be up for sharing some details on what the solution was? Asking as this would be super helpful to other folks in the Community here that having similar trouble with Pipedrive too. 

If not, it looks like the issue might be to do with what’s been selected for a custom field called “Location” or that has “location” in it’s name. I say that as I’m seeing what appears to be the start of the word “location” in the error message (though it could also be called “local” or something else that starts with “loca”):


If it’s a Dropdown menu type of field then the issue might be that it’s expecting an ID number for the location instead of a name of the location (see: Add custom values to dropdown menu fields in Zaps). In which case you might want to look at using a lookup table to convert the location. If you’ve not used lookup tables in Zaps before you find out more about how to set them up here: Create lookup tables in Zaps.

Looking forward to hearing from you on this!