Skip to main content
Answer

How to create two Modern UI customisations on the same screen?

  • November 20, 2025
  • 5 replies
  • 49 views

Forum|alt.badge.img+1

I have a customisation that adds a field to AP301000 - it’s part of a project that we’re deploying to pretty much all our customers.

I’ve another customisation that adds a very different set of fields to the same screen, and that will be deployed to a subset of our customers. (So it wouldn’t make sense to combine the projects at all.)

When I come to publish the second project, it fails with the error message:

The [published project] and  customization projects cannot be merged because they contain the duplicate AP301000 object.

 

The published typescript file has:

import {
  PXFieldState
} from "client-controls";
import {
  AP301000,
  APInvoice_CurrentDocument
} from "src/screens/AP/AP301000/AP301000";

export interface AP301000_PinnacleA_generated extends AP301000 {}

export class AP301000_PinnacleA_generated {}

export interface APInvoice_CurrentDocument_PinnacleA_generated
  extends APInvoice_CurrentDocument {}
export class APInvoice_CurrentDocument_PinnacleA_generated {
  UsrQueryReason: PXFieldState;
}
 

The (currently) unpublished file has:

import {  PXFieldState } from "client-controls";
import {
  AP301000,
  APInvoice_Document
} from "../AP301000";


export interface APInvoice_Document_PinnacleB
  extends APInvoice_Document {}
export class APInvoice_Document_PinnacleB {
  UsrCuryDeduction: PXFieldState;
}

 

What do I need to do to make these play nicely with each other??

 

Thanks!

Best answer by allisterchambers48

Having removed all Modern UI customisations from projectB, leaving projectA published with Classic and Modern changes on AP301000, and projectB having only Classic changes. I still get that error message. So it’s nothing to do with the .ts file on projectB as I get the error even when that file has been deleted.

 

However, all this pain and all the errors go away when I change the projects so that they have different Levels!

 

Having both projects set to Level 4 is clearly a mistake.

5 replies

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

} from "../AP301000";

I don't think this is the problem (yet), but it will be a problem eventually. The first 'from' is the correct way to do it.


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

When are you getting this error? Does it reach the Modern UI compile?


Forum|alt.badge.img+3

What are the names of your Modern UI files in both customizations? I'm not completely sure, but if they have the same name, try assigning unique names to each of them. I’ve created multiple customizations for the same screen and haven’t encountered such errors so far.


Forum|alt.badge.img+1

When are you getting this error? Does it reach the Modern UI compile?

The error is pretty much the first thing to appear.

And makes no difference if it imports from "src/screens/AP/AP301000/AP301000";

The published file is in:

C:\AcumaticaTenants\[tenant]\FrontendSources\screen\src\customizationScreens\Company\screens\AP\AP301000\extensions\AP301000_[projectA].ts

 

The unpublished in:

C:\AcumaticaTenants\[tenant]\FrontendSources\screen\src\development\screens\AP\AP301000\extensions\AP301000_[projectB].ts


Forum|alt.badge.img+1

Having removed all Modern UI customisations from projectB, leaving projectA published with Classic and Modern changes on AP301000, and projectB having only Classic changes. I still get that error message. So it’s nothing to do with the .ts file on projectB as I get the error even when that file has been deleted.

 

However, all this pain and all the errors go away when I change the projects so that they have different Levels!

 

Having both projects set to Level 4 is clearly a mistake.