cancel
Showing results for 
Search instead for 
Did you mean: 

Field remains read-only for edit type "String", wpf client

Former Member
0 Kudos

Hi,

I am having a object screen set and a screen.

I created a field with the edit type "String". What I want is an editable field on the screen.

But the field remains read-only.

I do not see any other configurations missing, please help.

I am using WPF client.

Thanks.

Kevin Hu

Tags edited by: Michael Appleby

Accepted Solutions (1)

Accepted Solutions (1)

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Kevin,

Are you using a transaction?  Fields are normally only editable when a transaction is running to capture the input from the user.

--Bill

Former Member
0 Kudos

Kevin,

If this is a Object Screen, Make sure you don't point the field pointed to any Object.

Stephen Streeter

Former Member
0 Kudos

Thanks Steve,

Can you rephrase your suggestion? Set "--None--" for the Object Property?

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Kevin,

Yes, that is what Steve is suggesting.  If you are not using a transaction screen but want to have an editable field (detail screen) you must make sure the field is not tied to an object property.

--Bill

Former Member
0 Kudos

Thanks Steve and Bill. It is working.

I reckon it was working on WM5.3 on WinCE, but it was more than a year ago. Poor memory I am.

Answers (2)

Answers (2)

Former Member
0 Kudos

There is a side effect.

If I set "--None--" for the Object Property, for those fields that needs multiple lines like Notes or Comments, I cannot use the word wrap or carriage return settings. The String edit type remains single line.

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Correct, but the intent of a detail screen is to display information in a read only state.  If you want to edit the date you should be using a transaction screen where this would not be an issue.

What are you trying to accomplish by not using a transaction screen?

--Bill

Former Member
0 Kudos

What I need is a screen like this, with tabs on top, and buttons at the bottom to save the fields.

Since transaction screens do not support tabs, I created an object screenset with screens(tabs) and config each field as below,

which brings me to the trouble with the Comments Field, where I need a multiple line editing field. But I found nowhere to make it happen even if I set the Field Heights to 3 or 4 or Auto.

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Normally we would treat this as a traditional display screen setup and then for each tab there would be an edit button to invoke a transaction to edit the same information displayed on the screen allowing the user to save or cancel.  Essentially exactly what you have except that when the edit is invoked it displays a transaction wizard screen for just the current tab.

The other possiblity would be to use Tile Edit controls on each tab to again display the data and switch to Edit mode on the tile and edit in place.

--Bill

Former Member
0 Kudos

It is not acceptable that user has to click through each tab and update 4 times instead of doing it in one screen. Jason also suggest to put all fields in one screen. Also not good enough when the list is long.

I did try the Tile Edit control on WPF client as a second option, but immediately gave up. It is behaving strangely, "Hide OK and cancel" and "In Progress Edit" option not working, and even if it is working the user has to click save button 4 times.

jason_latko
Active Contributor
0 Kudos

Kevin,

To make your comments field multi-line, you need to set the object and transaction comment string property parameter to checked for "Word wrap" in the property definitions.  You may also want to allow carriage returns there.  This will then respect your field height on screen.

You could also change your silent transaction triggered by your "Save" button to save values from all 4 screens at once, not just the screen you are on.  In the transaction, just point to the screen specifically to scrape the value from it:  Initial Value is "From Other Object".  Then set to: Whatever Screen Set -> Whatever Screen -> Whatever field.  You can point to all 4 screens this way in the same transaction.

Jason Latko - Senior Product Developer at SAP

Former Member
0 Kudos

Jason Thank for the reply.

In order to make my field editable in a non-transaction screen, I have to set the "Object Property" to None, as you can see from the attached image above.

In this case, it bypassed the chance for me to set the "work wrap" and "carriage" definitions.

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Kevin,

You are correct, you can only set a word wrap and carriage return setting if it is tied to an object property.

I don't think you are going to get a better solution.  I would personnaly go with either a multi-screen transaction wizard or sepate edit options for each tab.

--Bill

jason_latko
Active Contributor
0 Kudos

Kevin,

Yes, sorry!  You are correct.  Forgot that we were not on a transaction screen.  Since you are on WPF, you could try Tile Edit controls on each tab.  This may be a prettier solution from a user interface perspective and would allow multi-line comments on both the display and edit screen sets..

Jason Latko - Senior Product Developer at SAP

Former Member
0 Kudos

Thanks Jason.

I have tried the "Tile Edit" option on WPF.

Here is some of my findings,

I set up an tile edit screen (transaction) like this.

And here is what I get from the created screen

If I focus on the first field and enter some value, the tile is NOT activated, see below

Until I focus on the second field and enter some value, the tile is activated. See below.

And also the "Hide Buttons" and "In Progress Edit" options are not working. Even if I select non or all or one of these two options will not change any behavior of the tile edit.

Is it a normal behavior of tile edit, or I run into some limitations or functions not implemented on WPF Client?

Kevin Hu

Former Member
0 Kudos

Kevin,

As this is a different question then when the thread was opened please start a new thread with this question.

Stephen

tahir_z
Contributor
0 Kudos

Hi Kevin,

Just leave edit field type as "--Default--"

Tahir