Added custom field is in all capitals

[former_member232129]

Hi experts,

i have added a custom textfield to an iview containing family relations (IT0021).

When i first added the field in the infotype, i accidently added a char255 field which did not allow non-capitals.

This was noticed and our customer wants this to be changed so he can fill in (like normal) non-capital characters.

The field in the infotype is changed to a custom zchar255 field, and now allows non-capital characters.

The iview i have added this field to, however, does not allow non-capital characters.

On our develop environment, i thought this was due to caching, so i waited a day, and the problem solved itself.

On the quality portal however, this doens't seem to help.

Can someone explain to me, how this happens, and how i can change the field so it allows non-capital fields?

Do i need to ask for a server-reset?

Thx in advance.

Rien

[Former Member · Accepted solution]

Rien, what kind of iView is this, transactional, WDA? Post a codelink. In fact remote iViews are simply providing the same functions you have on your backend, without any limitations as far I know. Are you noticing any browser errors or default trace entries by sending the data?

cheers

[former_member232129 · Accepted solution]

Hi  Lawrence,

It's an iview containing the In Case of Emergency. WDA.

It is true that they should resemblance the backend, that is why i am posting here, for advice to how it's possible i dont see the same

I dont know what you mean by codelink.

There are no errors, when the field is filled in, and going into the next step "check", the whole field is in capitals. In the backend, the values are stored in capitals aswell.

When filling in the field in the backend directly (pa30), you can actually save non-capitals.

This was as designed before as i picked the wrong domaintype. I changed it in the backend, but it doenst look like the ivew changed along with it.

Thanks for the fast responce by the way, appreciated.

[Former Member · Accepted solution]

Sure, you are welcome. The iView you have mentioned has properties, one of them is codelink. This one will point you the actual java program the iView use, in your case it will be the EP WDA wrapper I guess. And: Im not talking about the errors on the UI, I assumed if there would be any, you would let us know. Im talking about JS stuff e.g., check it with the browser debug tools and the default trace of EP. Do you see something there? If not, hang in with the SE80 in your backend, debug (dont forget to measure the traffic), this will probably bring you closer to a solution. The question I would ask my self if I would be you is: are the data you have entered leaving the portal correctly or is this transformation to only capitals (I hope I got you right here) is happening on the backend?

R. v. d. Voorden wrote:

This was as designed before as i picked the wrong domaintype. I changed it in the backend, but it doenst look like the ivew changed along with it.

due this, I would assume its on the backend, since you changed the application. Caching stuff is good approach. In fact this remote iView should be called "live", but there is browser and EP cache. Empty it, restart the EP if necessary, just to be sure. Dont have an idea if ABAP is cachnig the stuff somewhere. I know, stupid queation: but did you activated your changes in the workbench for sure?

cheers

[former_member232129 · Accepted solution]

Lawrence,

i changed evertything, as far as needed, it's an QAS system, when i transport things, im not sure i can activate them, or have to for that matter.

I will ask for a restart of the portal, the DEV system had the same issue, and this apparently solved itself after a day (probably caching).

Thanks for the tips, if the restart fails, i will try some debugging.

[former_member232129 · Accepted solution]

Lawrence,

just wanted to let you know that the restart fixed the issue, it was due to caching after all.

Thanks again for the help!

[Former Member · Accepted solution]

Well done Rien, thank you for feedback. Additional to this topic, if a restart is not an option:

cheers

[harsha_jalakam]

Hi Rien,

Just wanted to confirm if my understanding is correct.  You have added a new field and have created a new domain for the same and it is displaying all the values in Capitals while you are retrieving the values.

It is based on the domain characteristics that all the values will be stored in capitals regardless in what you have entered the text. If you want to save the data in all small letters or in the way user has entered the data, then a conversion sub-routine must be written to that particular domain.

It is better if you are reusing the domain for the field you have created. Just check the field domain, which exactly fits your requirement and pick it up and use this for your new field.

Regards,

Harsha

[former_member232129]

Hi Harsha,

it is true that i picked the wrong domaintype (one that only allowed capitals).

That is why i changed it into a type that does allow non/capitals.

My issue is that the field on the portal, still does not allow non-capitals, while the backend(pa30) does allow it.