Increasing length of the Pay Item CD field

Hi @Leonardo Justiniano ,

Thanks for your response. I have created the Database Script the way you mentioned, so it should be all good on the database side. For the on-screen field, I have added the PXDBString change to the field, as shown below, but it still doesn't do anything.

It may have something to do with the fact that no attributes seem to appear in this screen, so I am not sure if the attributes are able to be amended. Is it blank for you as well?

Are there any other ways for the length of on-screen fields to be extended?

Kind regards,

Andrew

@AndrewA

The way you are defining the change sounds good “Replace Original” You are missing, though, the labeling. You need to add on a replace:

[PXUIField(DisplayName = ".. Label ..")]

Sometimes the screen editor does not show the base definition properly (glitches or ISV components). For I can see also in your screenshot you are trying to modify a field from a 3rd party provider (ISV) or Internal development. I recommend to request the change to them. Otherwise, inspect the record and determine the class and then implement a cache attached replacement:

...
using MYOB.AdvanceLive.People.Objects.PP;

public class XYZ_Graph_Extension : PXGraphExtension<XYZ_Graph>
{

...

  [PXMergeAttributes(Method = MergeMethod.Replace)]
  [PXUIField(DisplayName = ".. LABEL ..")]
  [PXDBString(20, IsKey = true, IsUnicode = true, InputMask = "CCCCCCCCCCCCCCCCCCCC")]
  protected void _(Events.CacheAttached<MPPayItem.payItemCD> e) { }

...

}

Also, as @Sagar Greytrix mentioned, take a look to the blog. If the DAC fields do not appear in the DATA ACCESS section you must have them declared in the CODE section as a DAC class. If it is an not there, must be an external library or the declaration is in another package, Find the package and make the change. As I stated above, you are at risk if the provider of the package comes with a new version which will override your change.