Hi,

Stephen is right about creating a new datatype instead of modifying an existing one.

In your case, your issue probably comes from the table "ATEXTRA".

It's in this table that AX3 datas are stored in the field "TEXTE".

If not already done, you need to update this field too and validate the table.

Regards,

Laurent

Thanks Stephen

Its Working Fine.

let me know which datatype I have to use which upto 4000 characters limit.

Regards

Gautam

Its charater data and have mixture of special charaters.

Regards

Gautam

Gautam, I have in the past used the ACPLAIN data type for this type of data.

Thanks Michael for reply

In Table Dictionary While I add new field error  messgae come.

Sage X3 Application Error

Text file length too long : 4995

Regards

.Gautam

Gautam, Use a length of 10. ACPLAIN length is measured in blocks of 512, so a length of 10 will handle 5120 characters.

True but the Issue is while I use ACPLAIN Datatype and even I enter length 1 or any length upto 10 it gives error Sage X3 Error -Textfile length is too long -4995.  Is there any another field in table  dictionary which I have to select.

Regards

True but the Issue is while I use ACPLAIN Datatype and even I enter length 1 or any length upto 10 it gives error Sage X3 Error -Textfile length is too long -4995.  Is there any another field in table  dictionary which I have to select.

Regards

I tried it by creating new table its working , I mean new table its taking length 10. but I  have to add it in ITMMASTER table.In ITMMASTER it  gives error Sage X3 Error -Textfile length is too long -4995. 

Is there any limitation.

Regards

Moreover problem is same , this field not reflecting in Selection Objects while using OBJECTS to create new selection window for new table  where I have added ACPLAIN field .

In selection window mean creating object can be add or sum two field values to show single record.

Regards

Gautam, 

It sounds like you might be running into a limitation of X3, or I might be misunderstanding you. It would be hard to tell without looking at what you're doing. I'd suggest logging a ticket with Sage or getting help from an experienced X3 partner.

Thanks Michael for your best feedback

.