BC31429: '<elementname>' is ambiguous because multiple kinds of members with this name exist in class '<typename>'

Help Integration Service
1

I’ve built an activity in Integration Service with Parameters:

image
image302×187 5.24 KB

And Response Fields:

image
image526×943 47 KB

image
image513×948 44.3 KB

Then when using this activity in a process I’m receiving an error:

image
image652×452 22.5 KB

If I convert TransmittalItem to JSON then I can see two entries for code and Code:

image
image338×107 3.18 KB

I’ve only got the one code output defined in Integration Service, how do I remove the duplicate?

2

@samuel.janetzki

Can you check your response fields from properties section of the activity whether there is any duplicate names are there as Code and code. that may be hidden sometimes, just give a deep look and find out and delete.

OR
If is there any chance that you can edit field name instead Code try to modify Status code or something like that

3

Resolved the issue, I needed to delete the existing Response Fields and recreate them starting with a lowercase letter:

image
image638×611 28.1 KB

So if field is returned in JSON response starting with a lowercase letter then the Response Field must start with a lowercase letter. If the field in the JSON response starts with an uppercase letter then the Response Field can start with an uppercase or lowercase letter.

4

Hi @samuel.janetzki,

Thanks for sharing the resolution — this will definitely help others facing the same BC31429 ambiguity issue.

The problem occurs because VB.NET treats member names in a case-insensitive way in certain scenarios, which can create conflicts between fields like:

Codecode

In Integration Service activities, the Response Fields should closely match the JSON response naming convention.

Resolution:

  • Delete the existing Response Fields
  • Recreate them using the exact casing from the JSON response
  • If the JSON field starts with lowercase, create the Response Field in lowercase as well

Example:

{  "code": 200}

Correct Response Field:

code

Using Code may trigger the ambiguity error.

Good catch on identifying the casing behavior.