Data Access Class for POLandedCostSplit

Bummer, thanks for checking that. "POLandedCostDetail" doesn't have everything that I need unfortunately.

@TimRodman 

oh okay. Could you please let us know that what is the info you want to get from POLandedCostSplit

Hi @TimRodman 
Since the DAC decorated with [PXHidden] attribute any class derived from it also will be hidden for 
Web api clients, instead of SQL view you can create a simple arbitary DAC class called PXProjection
with basic BQL select statement, you can create the class with any meaningful name (eg:ExposedPOLandedCostSplit) and copy paste all the properties from POLandedCostSplit to your newly created class, then add the BqlField = typeof(POLandedCostSplit. <property name>)] parameter inside the data type attributes of all properties you copied from original POLandedCostSplit

you can use the below code to decorate the new arbitary DAC (PXProjection DAC)
[PXProjection(typeof(Select<POLandedCostSplit,
            Where<PX.Objects.CS.int1, Equal<PX.Objects.CS.int1>>>), Persistent = false)] 
[Serializable]
This Projection DAC will act exactly same like SQL View but it’s the approved method by Acumatica 

Hi @TimRodman 

I concur with @KishoK. We can create a PXProjection to the “POLandedCostSplit” DAC and create a GI with Projection DAC.

This way we can get the required details.

Thank you @KishoK and @Naveen B for the ideas. I was trying to avoid a Customization Project, but I’ll look into using a PXProjection DAC.