Skip to main content
Solved

Removing Custom Fields

  • February 4, 2022
  • 4 replies
  • 539 views

Hi,

We are looking to switch some of our custom fields to be unbound. I have switched the custom fields in our Sales Order extension DAC with no problems. However, following these same steps with our Shipment extension DAC, I have run into some issues. I made the changes to the fields in the DAC, but now the fields are completely missing from the Screen page in the Project Editor.

Adding the fields back in through the Project Editor UI will give a “duplicate field” error, or it will add the field and not recognize that it exists in the customization code.

Has anyone run into this before? I have included the code changes below if that helps.

 

The code was changed from;

[PXDBString(20)]
[PXUIField(DisplayName = "Sample")]
public virtual string UsrSample { getset; }
public abstract class usrSample : IBqlField { }

To;

[PXString(20)]
[PXUIField(DisplayName = "Sample", Enabled = false)]
[PXDBScalar(typeof(Search<test.message, Where<test.docNbr, Equal<SOOrder.orderNbr>, 
     And<test.docSubType, Equal<SOOrder.orderType>>>>))]
public virtual string UsrSample { get; set; }
public abstract class usrSample : Data.BQL.BqlString.Field<usrSample> { }

Thank you!

Best answer by Hughes Beausejour

Reboot the server hosting Acumatica website. This will ensure a few reset occurs. Check if the old/duplicate field is still lingering. If it is, there’s a very high chance you have declared a duplicate field in runtime customization and or compiled library, You should thorouhgly search for it in that case.

View original
Did this topic help you find an answer to your question?

4 replies

Forum|alt.badge.img+8
  • Semi-Pro I
  • 715 replies
  • February 4, 2022

Hi @noahmiller02 As a workaround, try adding new naming for the new Unbounded fields instead of using the same names that you have used before.

Thanks


Hughes Beausejour
Acumatica Employee
Forum|alt.badge.img+2
  • Acumatica Developer Support Team
  • 91 replies
  • Answer
  • February 6, 2022

Reboot the server hosting Acumatica website. This will ensure a few reset occurs. Check if the old/duplicate field is still lingering. If it is, there’s a very high chance you have declared a duplicate field in runtime customization and or compiled library, You should thorouhgly search for it in that case.


Naveen Boga
Captain II
Forum|alt.badge.img+19
  • Captain II
  • 3409 replies
  • February 7, 2022

HI, @noahmiller02  At the beginning of Acumatica development training, I also faced similar kinds of issues. Below are are you can check.

  • Runtime folder
  • If DLL is present, check the source code
  • you can use Ctrl + Shift + F ==> and search with that field name i.e. UsrSample

Hope this helps!!

 

 


  • Author
  • Freshman II
  • 9 replies
  • February 7, 2022

Hi All,

Thank you for getting back to me so soon. I appreciate your responses. I found remnants of the old fields in the .aspx page files. I removed those references and restarted the website server and that did the trick! Thank you again.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings