Incompatible type error when calling REST API

[UniKev]

I’m working on a Powerapp which is intended to be used to register applicants for casual work at the University.

The app consists of a number of Screens where the user will answer questions via a combination of radio buttons, checkboxes and the odd textinput field.

The answers are then passed to a REST API in a custom connector which does the updating.

This API is called in the onSelect property of a button. The code for this property is

//Create global records with required value pairs

// Bank Details

Set(glob_bankdetails,{bankSortCode:TextInputUpdBankSC.Text,bankAccountNumber:TextInputUpdBankAN.Text});

//EqualOps

Set(glob_equalopps,{legalGender:LabelMFValue.Text,

legalGenderRegistered:LabelLegGenValue.Text,

chosenGender:LabelSexValue.Text,

ethnicity:LabelEthnicityValue.Text,

nationality:TextInputNationality.Text,

nationalIdentity:LabelNatIdenValue.Text,

religousBelief:LabelRelBeliefValue.Text,

sexualOrientation:LabelSexOrValue.Text,

disabledTwo:CheckboxDisabledTwo.Value,

disabledSpecificLearning:CheckboxDisabledSpecificLearning.Value,

disabledGeneralLearning:CheckboxDisabledGeneralLearning.Value,

disabledCognitive:CheckboxDisabledCognitive.Value,

disabledHealth:CheckboxDisabledHealth.Value,

disabledPhysical:CheckboxDisabledPhysical.Value,

disabledHearing:CheckboxDisabledHearing.Value,

disabledBlind:CheckboxDisabledBlind.Value,

disabledOther:CheckboxDisabledOther.Value,

disabledDoNotWishToAnswer:CheckboxDisabledNotAnswer.Value,

welshUnderstand:LabelWelshUndValue.Text,

welshRead:LabelWelshReadValue.Text,

welshWrite:LabelWelshWriteValue.Text,

welshSpeak:LabelWelshSpeakValue.Text});

//Starter Decleration

Set(glob_starterdec,{optionLetter:RadioStartDec.Selected.Value,studentLoan:LabelStudLnValue.Text});

//Call API to register details

CasualWorkerSupportService.registerInternalWorker(LabelCanolfanId.Text,{bankDetails:glob_bankdetails,niNumber:LabelNiNumb.Text,starterDecleration:glob_starterdec,equalOpsData:glob_equalopps});

Navigate(ScreenConfirm,Fade)

So I’ve used global variables to create records and passed the record name as values into the API where required. However I get the following error message from the button

‘Incompatible type. The ‘ethnicity’ column in the data source you’re updating expects a ‘Number’ type and you’re using a ‘Text’ type’.

The value I’m passing to ‘ethnicity’ is in field LabelEthnicityValue.Text. This is derived from a radio button field as follows

If(RadioEthnicity.Selected.Value="White",0,

RadioEthnicity.Selected.Value="Gypsy or Traveller",1,

RadioEthnicity.Selected.Value="Arab",2,

………………………………………

………………………………………)

As you can see I’m passing the actual value as a number not a string.

I’ve tried fixing it by adding a Value statement  to the above  i.e. Value(If(……..)) but that doesn’t change the error.

I’ve also tried enclosing the field name within the global in a value tag  i.e. ethnicity:Value(LabelEthnicityValue.Text) but then I get ‘Missing column. Your formula is missing a column ‘religiousBelief’ with a type of ‘Number’.’

So I’m stumped. I’m a total beginner with Powerapps and I’m sure there are more elegant ways of deriving a value from a radio button. However, I’m not convinced that it’s my fudge that’s the issue here.

I’d be grateful for any advice anyone might have.

Thanks in advance,

Kevin

[timl]

Hi Kevin,

To diagnose this, I'd suggest that you retrieve your ethnicity value and store it in a variable.

Set (EthnicityID,
     If(RadioEthnicity.Selected.Value="White",0,
       RadioEthnicity.Selected.Value="Gypsy or Traveller",1,
       RadioEthnicity.Selected.Value="Arab",2,
       ………………………………………
       ………………………………………)
)

I'd then add a label control and set the Text property to EthnicityID. The purpose of this is to be able to inspect your EthnicityID before passing it to your API. If you do this, does EthnicityID show up as a numeric value?

[RandyHayes · Accepted solution]

@UniKev 

From what I see in your Formula, the real issue is with the ethnicity value.  As the error suggests, you need a numeric value, not a string.  You are assigning a string to it.

Changing your variable to have the Value function in it is what you want.  However, as you mentioned, you did that and got another error - I might suggest that you fixed the ethnicity error, but then have another error to deal with. In this case, it seems that your religousBelief is misspelled.  It should be religiousBelief (as the error suggests).  AND, it also suggests that it is a numeric value...so you might need the Value function on that as well.

chosenGender:LabelSexValue.Text,
ethnicity:Value(LabelEthnicityValue.Text),
nationality:TextInputNationality.Text,
nationalIdentity:LabelNatIdenValue.Text,
religiousBelief:Value(LabelRelBeliefValue.Text),

I hope this helps you get to the next step...or at least the next error.

[UniKev]

Thank you both for taking the time to reply.

---

@RandyHayes wrote:

@UniKev 

From what I see in your Formula, the real issue is with the ethnicity value.  As the error suggests, you need a numeric value, not a string.  You are assigning a string to it.

Changing your variable to have the Value function in it is what you want.  However, as you mentioned, you did that and got another error - I might suggest that you fixed the ethnicity error, but then have another error to deal with. In this case, it seems that your religousBelief is misspelled.  It should be religiousBelief (as the error suggests).  AND, it also suggests that it is a numeric value...so you might need the Value function on that as well.

chosenGender:LabelSexValue.Text,
ethnicity:Value(LabelEthnicityValue.Text),
nationality:TextInputNationality.Text,
nationalIdentity:LabelNatIdenValue.Text,
religiousBelief:Value(LabelRelBeliefValue.Text),

I hope this helps you get to the next step...or at least the next error.

---

It was indeed my typo when writing 'religious' that was the issue. Once I fixed that the error messages disappear.

Strangely, that field doesn't moan about the text value even though it's derived in exactly the same way.

Can't believe I didn't notice the typo. However, in my defence the code editor is pretty awful and I find it difficult to easily write nicely formatted code. (That's my excuse and I'm sticking to it 😉

Once again thanks,

Kevin

[RandyHayes]

@UniKev 

Excellent!!  Yes, strange about the other field not complaining...hmmm

I agree, when it comes to the individual fields of a record (that the designer "should" know) it would be really nice if there was some auto-suggest text in the Formula editor.

The messages kind of taunt you..."hey you forgot this field...I know what it is, but I'm not gonna tell ya!"

[timl]

Well done @RandyHayes - well spotted!