[SalesForce] Reason behind element value must resolve to a String type!

I faced an issue with <apex:inputText> while using disabled attribute with it.

The scenario is i can disable and enable the <apex:inputText> using a checkbox.

<apex:inputText> is binded with an Integer variable.

But when i enable the

<apex:inputText>

i get error : element value must resolve to a String type!

I tried these workarounds given in this post
apex:inputText disabled binding causing "element value must resolve to a String type!"

But the above workarounds changes the appearance , the goal is not achievable.

When i tried binding <apex:inputText> with String , the functionality worked fine , however now i have to make use of Integer.valueOf(myStringVariable) everywhere i need to do calculations in my code.

I just want to know the reason behind this error element value must resolve to a String type!

Why this doesn't work with integer value.

Best Answer

This looks to be a bug in Visualforce - its been around since 2008 by the look of this post on the Developerforce Discussion Boards:

https://developer.salesforce.com/forums/ForumsMain?id=906F0000000951yIAA

The best I've been able to do with this is to have the underlying property still stored as an Integer, but have a string based getter/setter for it that converts to/from a string. That way I can use the property as an Integer within my code and I just have to convert it once.

You'll need an answer from Salesforce as to why it works this way - given that people have been complaining about this behaviour for nearly 6 years, it feels like they might think its working correctly. Although Doug Chasman does suggest its a bug in the developerforce post above.

Related Solutions

[SalesForce] apex:inputText disabled binding causing “element value must resolve to a String type!”

Can you just use outputText instead if it needs to be disabled? Not the same appearance but might work for you?

<apex:outputText id="impressions" value="{!drop.impressionsRequested}" rendered="{!dropObj.impressionsDisabled}"/>

<apex:inputText id="impressions" value="{!drop.impressionsRequested}" rendered="{!NOT(dropObj.impressionsDisabled)}"/>

Or instead out output text you could just use a disabled HTML input element so it would maintain the same look:

<apex:outputPanel layout="none" rendered="{!dropObj.impressionsDisabled}">
    <input type="text" value="{!drop.impressionsRequested}"/>
</apex:outputPanel>

[SalesForce] Type mismatch for

You say you are having issues when deploying correct? Any chance the controller already exists in the org you are deploying to? Any chance you missed the controller in the new deploy?

One scenario I have run into in the past is that the validation Salesforce runs can be a bit tricky when dealing with controllers and Visualforce. For instance:

You have two files in production, one for the controller and one for Visualforce.
You make changes to both files in a dev org/sandbox.
You deploy both files back to production, but validation fails on the Visualforce page. You get an error indicating a missing field, mismatched type, etc. indicating that the controller doesn't have that field.
You verify both files work fine in dev and are completely confused at this point. The problem I have found is (and this is completely speculating but I have seen it before). The issue is that the production org is validating the Visualforce against the old Apex code before it deploys the updated Apex code as part of the deploy.

To workaround this issue, if you can, you need to either delete the production instance of the code or comment out the Visualforce as part of the deploy and then uncomment it in production. There is no exact science to it, and this may not even be the real reason behind my issues in the past, but I have experienced some very strange things during deploys in the past. Good luck!

Best Answer

Related Solutions

[SalesForce] apex:inputText disabled binding causing “element value must resolve to a String type!”

[SalesForce] Type mismatch for

Related Topic