Highlighted
Absent Member.
Absent Member.
315 views

Chaging th size of a field

Jump to solution
Hello

I have the field Solution in all the forms in Service Desk: Incident, Service Call, Change and Problem. We change the name of this field to "Respuesta a Usuario".

As you can see in the attachment the same field in different modules have different size.

We want to know how can we set up this field in Incident of the same size of Service Call (long text)

Is it possible to change the field size without changing the field from 255 to 4000 characters?



0 Likes
1 Solution

Accepted Solutions
Highlighted
Absent Member.
Absent Member.

Re: Chaging th size of a field

Jump to solution
You can't change the field size. What you can do is using a custom 4k field and name it "Respuesta a Usuario"
menes fhtagn

View solution in original post

5 Replies
Highlighted
Absent Member.
Absent Member.

Re: Chaging th size of a field

Jump to solution
You can't change the field size. What you can do is using a custom 4k field and name it "Respuesta a Usuario"
menes fhtagn

View solution in original post

Highlighted
Absent Member.
Absent Member.

Re: Chaging th size of a field

Jump to solution
Actually you can change the field's size directly in the database (you'll loose support though) and SD will use it.
Highlighted
Absent Member.
Absent Member.

Re: Chaging th size of a field

Jump to solution
Hi,

better to use another field and copy the data from the old field to the new field. Changing the size at the DB level will affect your support and may have an impact on migration (you just never know) if you choose to migrate at a later date.

Radovan has developed an update all featrue that will allow you easily move the data from one field to another without having to use DB rules and a trigger.
Highlighted
Absent Member.
Absent Member.

Re: Chaging th size of a field

Jump to solution
" better to use another field and copy the data from the old field to the new field. "

Hey Mark,

While I respect your Mighty-Pharoh-Hat-Power, if Claudia is running OVSD 5.1 the old field to new field copying is just going to eat up one of her precious few custom fields. It works, but the sacrifice is worth noting.
Highlighted
Absent Member.
Absent Member.

Re: Chaging th size of a field

Jump to solution
Mighty-Pharoh must respond 🙂

-=R=- the screen shots looks like 4.5 but anyway if under SP 17 ish they have the same probem witl "limited" custom fields. The can update the DB directly and increase the field size there but if they have any problems they could void warranty support. So with tta in mind I prefer to advise people to use an existing larger field. yes you will be one 4k field less but its better to be down the field and in warranty then to void the warranty conditions and fal out of support.

So thats the context of the recommendation. by the way I really struggle with the default problem fields. pre SP 17ish there just was not enough of them.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.