Skip to main content
Answer

Modern UI customisation of AP303000 (Vendors) screen not possible due to Errors

  • November 17, 2025
  • 8 replies
  • 102 views

Forum|alt.badge.img+1

Using an instance of 25.200.0020 (clean install), I need to customise screen AP303000 to add some fields (specifically AddressLine3), but on opening the Modern UI Editor from the Customization Project Editor for that screen, I get the error message:

 

In HTML extension “C:\..\FrontendSources\screen\src\screens\AP303000\extensions\AP303000_PersonalDataPrivacy.html” for screen ‘AP303000’ child node ‘QP-FIELDSET’ has AFTER attribute with ‘#groupAccountAddress’ but screen HTML doesn’t contain any elements that satisfies such querySelector.

I can work around this locally by renaming the source files AP303000_PersonalDataPrivacy.html and .ts (adding a suffix of .x). But I’m concerned that the same hack won’t be possible in production.

 

Best answer by Dmitrii Naumov

I’ve checked in the latest version and the issue is still there. 

Reported to engineering to fix. 

 

8 replies

darylbowman
Captain II
Forum|alt.badge.img+15

The latest available version of 25 R2 is 25.200.0248.

 

I believe there was a previous version that had some issues.


Dmitrii Naumov
Acumatica Moderator
Forum|alt.badge.img+7
  • Acumatica Moderator
  • Answer
  • November 17, 2025

I’ve checked in the latest version and the issue is still there. 

Reported to engineering to fix. 

 


darylbowman
Captain II
Forum|alt.badge.img+15

Perhaps a workaround is to turn off the data privacy stuff? I have customized that screen and it was fine, but I don’t think I had that enabled.


Forum|alt.badge.img+1

Thanks guys. BTW, my typo. I quoted the wrong version number previously. I’ve been working on 25.200.0248.


Forum|alt.badge.img+1

The .ts has a test on PX.Objects.CS.FeaturesSet+GDPRCompliance, but the .html include file doesn’t have that.

I don’t have GDPR Compliance Tools enabled, so it looks like the include file is being processed regardless.


Forum|alt.badge.img+1

I’ve encountered a similar problem with an extension file that I’ve created.

I’m extendeding screen AP303000, and initially the HTML is visible in Modern UI Editor.

When I add an extension file in ..\FrontendSources\screen\src\development\screens\AP\AP303000\extensions e.g. with: 


<template>

        <field name="AddressLine3" after="#groupAccountAddress [name='AddressLine2']"></field>

</template>

 

That same error appears: “In HTML extension [] for screen ‘AP303000’ child node ‘FIELD’ has AFTER attribute with #groupAccountAddress [name=’AddressLine2’] but screen HTML doesn’t contain any elements that satisfy such querySelector.

That extension does successfully add AddressLine3 in the desired location. But the error means I can’t view the resulting HTML unless I comment out the extension.


darylbowman
Captain II
Forum|alt.badge.img+15

I think this will help you.

 

EDIT:

That extension does successfully add AddressLine3 in the desired location.

Or maybe not


JKurtz29
Varsity II
Forum|alt.badge.img+1
  • Varsity II
  • December 2, 2025

I’ve encountered a similar problem with an extension file that I’ve created.

I’m extendeding screen AP303000, and initially the HTML is visible in Modern UI Editor.

When I add an extension file in ..\FrontendSources\screen\src\development\screens\AP\AP303000\extensions e.g. with: 


<template>         <field name="AddressLine3" after="#groupAccountAddress [name='AddressLine2']"></field> </template>

 

That same error appears: “In HTML extension [] for screen ‘AP303000’ child node ‘FIELD’ has AFTER attribute with #groupAccountAddress [name=’AddressLine2’] but screen HTML doesn’t contain any elements that satisfy such querySelector.

That extension does successfully add AddressLine3 in the desired location. But the error means I can’t view the resulting HTML unless I comment out the extension.

To add AddressLine3, wouldn’t it be best to just use the built in Screen Configuration utility instead of using a customization?

Also, just taking a guess here, but could you name your extension something like AP303000_zzAddress3.html to see if the loading sequence matters?