Creating new SOOrder PXSelector in CRCAse

@RolandZipper Do you want to create a Sales Order Nbr (Selector) custom field in the above screen?

@Naveen Boga yes

@RolandZipper  Please add the field like below for the Sales Order Nbr lookup field.

	[PXDBString(15, IsUnicode = true, InputMask = ">CCCCCCCCCCCCCCC")]		
		[PXUIField(DisplayName = "Test Inv", Visibility = PXUIVisibility.SelectorVisible)]
		[SO.RefNbr(typeof(Search<SOOrder.orderNbr, Where<True, Equal<True>>, OrderBy<Desc<SOOrder.orderNbr>>>), Filterable = true)]
		public string UsrCorrespOrder { get; set; }
		public abstract class usrCorrespOrder : PX.Data.BQL.BqlString.Field<usrCorrespOrder> { };

Thank you for the reply.

As expected acumatica shows following behavior when compiling:

\App_RuntimeCode\CRCaseMaint.cs(29): error CS0234: The type or namespace name 'RefNbrAttribute' does not exist in the namespace 'PX.Objects.SO' (are you missing an assembly reference?)

\App_RuntimeCode\CRCaseMaint.cs(29): error CS0234: The type or namespace name 'RefNbr' does not exist in the namespace 'PX.Objects.SO' (are you missing an assembly reference?)

\App_RuntimeCode\CRCaseMaint.cs(29): error CS0246: The type or namespace name 'SOOrder' could not be found (are you missing a using directive or an assembly reference?)

\App_RuntimeCode\CRCaseMaint.cs(29): error CS0246: The type or namespace name 'SOOrder' could not be found (are you missing a using directive or an assembly reference?)

\App_RuntimeCode\CRCaseMaint.cs(29): error CS0246: The type or namespace name 'Filterable' could not be found (are you missing a using directive or an assembly reference?)

@RolandZipper Can you share the customization package here?

its empty apart from:
 

and
 

@RolandZipper  Why are you adding the Extended field in the Graph Extension. This is completely wrong.

Please extend the DAC of CRCase and add this field also include the below namespace in the DAC Extension and publish the package.

using PX.Objects.SO;

Hello, 
Sorry for my late reply, I wish you a happy new year.
You are completly right I added it wrong. 

 

This is how I added it now, some assembly references seem to be missing.

best regards.

@RolandZipper  Happy New Year!!

Please export your customization package and share it here for our review.

Here it is

@RolandZipper you have shared the XML file, which I can not import into my instance. 

Please export the customization package using EXPORT button from the Customizations Projects screen and share it here.

Here is the screenshot for your reference.

I’m sorry, here is the file

Thank you.