[NoFieldFound]No field found: Lead._CustomFieldName

[Matthew_Bloom]

Hey there,

I’m using the xml-rpc api to fetch opportunities including some custom fields. My customer that my company’s software integrates with has confirmed that the custom fields do still exist on their end.

Here’s a gist that shows the requests I’m making.

The first request returns the custom fields for their opportunity module. Its response includes four custom fields.

The second request includes those four custom fields (including the underscores, which most NoFieldFound issues have been missing on this forum) and returns an error of NoFieldFound.

https://gist.github.com/MatthewJBloom/053bec8a6bd671e9288a4b133d051212

I’ve also researched through all of the following forum posts:
https://integration.keap.com/search?q=%5BNoFieldFound%5DNo%20field%20found

…in addition to this somewhat relevant forum post:

Intermittent No Field Found errors for existing fields

I work on a piece of software that connects to a number of different Infusionsoft databases via the xml api. About last week, across the board our these different instances of software started getting intermittent No Field Found errors retrieving objects from Infusionsoft (Contacts, Companies etc.). I have struggled to reproduce in a dev environment as it happens only intermittently and for legitimate fields (legit as in they do exist). [image] Did something change in the API that anyone know…

Thanks for reading, hoping to get this figured out as I can not see an issue in my requests.

P.S. I’ve tried throwing some random stuff at it like appending 0, 1, 2, 3, etc at the end of the custom field name in case it had been deleted & recreated. I’ve tried using the field id instead of field name. I’ve tried appending ._fieldId. Just for some additional context of what I’ve tested already ^. Thanks!

[Matthew_Bloom]

Hey there,

This turned out to be an odd one. The customer I was supporting had actually disabled their opportunity module.

Quite curious that I could still get records returned even though the module was disabled and that the error message was describing a missing field instead of a disabled module.

Just leaving this here in case anyone else sees this