Possible to dynamically make hidden field visible?

You can configure the visibility from the Fields menu.

But if you need something more complicated than simply always hidden or always shown, then you will need to configure a condition and apply that instead of true.
 

Thanks Samvel. That’s part of my issue. When I go to conditions, I only see default fields to set the conditions, but the custom user Usr “New Fields” I need are not in the dropdown to select:

I need to grab the values from a field like UsrNewField.

swartzfeger wrote:

Samvel Petrosov wrote:

You can configure the visibility from the Fields menu.

But if you need something more complicated than simply always hidden or always shown, then you will need to configure a condition and apply that instead of true.

Thanks Samvel. That’s part of my issue. When I go to conditions, I only see default fields to set the conditions, but the custom user Usr “New Fields” I need are not in the dropdown to select:

I need to grab the values from a field like UsrNewField.

 

As far as I know that dropdown only works with the header record of the page. So in your case the page is CR304000 - Opportunities and the header record is CROpportunity.

Is you custom field added to CROpportunity or some other table? I don’t think it supports anything outside of the header record/table

Samvel Petrosov wrote:

swartzfeger wrote:

Samvel Petrosov wrote:

You can configure the visibility from the Fields menu.

But if you need something more complicated than simply always hidden or always shown, then you will need to configure a condition and apply that instead of true.

Thanks Samvel. That’s part of my issue. When I go to conditions, I only see default fields to set the conditions, but the custom user Usr “New Fields” I need are not in the dropdown to select:

I need to grab the values from a field like UsrNewField.

 

As far as I know that dropdown only works with the header record of the page. So in your case the page is CR304000 - Opportunities and the header record is CROpportunity.

Is you custom field added to CROpportunity or some other table? I don’t think it supports anything outside of the header record/table

 

Correct, it’s added to another custom table called OpportunityQuotePricing (which is what I was afraid of… the condition only works for native fields in the header).

I think I may need to add something like this in my dropdown attributes:

[PXUIVisible(typeof(Where<TSMIGOpportunityQuotePricingExt.UsrCMoldPartTexture.IsEqual<1>>))]

​@swartzfeger  We can’t add the conditions for the Line level fields in the workflow.

I suggest you to write the code using PXUIVisible for the line level fields.

[PXDBInt]
[PXIntList(new int[] {0, 1}, new string[] {"No", "Yes"})]
[PXUIVisible(typeof(Where<TSMIGOpportunityQuotePricing.UsrCMoldPartTexture.IsEqual<int1>>))]
[PXUIField(DisplayName="Shot Peen 330 or Less?")]

Hi Naveen, I implemented PXUIVisible and got the following error. The only thing that I can think of is that Acumatica seems to have CAPITALIZED the field name and the field name is case sensitive (I did not create the field name with all caps!)

[2025-03-21 04:51:57.744] Patching the file c:\deployment\sites\SB00008580\Customization\SB00008580\siterootValidation\siterootWebsite\App_RuntimeCode\TSMIG_TSMIGOpportunityQuotePricing_extensions.cs
[2025-03-21 04:51:59.042] Done
[2025-03-21 04:51:59.048] Validating Binary Files
[2025-03-21 04:51:59.838] Validating Sql Scripts
[2025-03-21 04:51:59.941] Validating the website c:\deployment\sites\SB00008580\Customization\SB00008580\siterootValidation\siterootWebsite
[2025-03-21 04:51:59.943] IIS APPPOOL\SB00008580
[2025-03-21 04:52:03.879] Building directory '\WebSiteValidationDomain\App_RuntimeCode\'.
[2025-03-21 04:52:15.675] \App_RuntimeCode\TSMIG_TSMIGOpportunityQuotePricing_extensions.cs(133): error CS0426: The type name 'UsrCMoldPartTexture' does not exist in the type 'TSMIGOpportunityQuotePricing'
[2025-03-21 04:52:15.676] \App_RuntimeCode\TSMIG_TSMIGOpportunityQuotePricing_extensions.cs(133): error CS0246: The type or namespace name 'int1' could not be found (are you missing a using directive or an assembly reference?)
[2025-03-21 04:52:15.679] \App_RuntimeCode\TSMIG_TSMIGOpportunityQuotePricing_extensions.cs(133): error CS0426: The type name 'UsrCMoldPartTexture' does not exist in the type 'TSMIGOpportunityQuotePricing'
[2025-03-21 04:52:15.684] Compiler time, in seconds: 15.7422876
[2025-03-21 04:52:15.690] Validation failed.

​@swartzfeger  If you are comfortable, can you please share the customization package?

Absolutely, thank you Naveen!

Hi ​@swartzfeger  I could not able to proceed to test this customization due to the below error.

Naveen Boga wrote:

Hi ​@swartzfeger  I could not able to proceed to test this customization due to the below error.

 

Sorry Naveen maybe try one of these…

​@swartzfeger  Getting same error. I DM’ed you the details and let’s connect if you are available and check this in your machine.

[PXUIVisible(typeof(Where<TSMIGOpportunityQuotePricing.UsrCMoldPartTexture.IsEqual<int1>>))]

I don’t see your full field declaration but generally in bql you would be using the abstract member, ie the lowercase TSMIGOpportunityQuotePricing.usrCMoldPartTexture as part of your query

Thanks Josiah, I did not know that and I will try!

Didn’t fly, the validation failed with this:

Building directory '\WebSiteValidationDomain\App_RuntimeCode\'.
\App_RuntimeCode\TSMIG_TSMIGOpportunityQuotePricing_extensions.cs(142): error CS0426: The type name 'usrCMoldPartTexture' does not exist in the type 'TSMIGOpportunityQuotePricing'
\App_RuntimeCode\TSMIG_TSMIGOpportunityQuotePricing_extensions.cs(142): error CS0246: The type or namespace name 'int1' could not be found (are you missing a using directive or an assembly reference?)
\App_RuntimeCode\TSMIG_TSMIGOpportunityQuotePricing_extensions.cs(142): error CS0426: The type name 'usrCMoldPartTexture' does not exist in the type 'TSMIGOpportunityQuotePricing'
Compiler time, in seconds: 16.6854327
Validation failed.

Can you share a screenshot of the full field declaration (including the DAC) of the usrCMoldPartTexture field, as well as the full declaration of the field you are putting this attribute on?

The bql field is what you should be using in your query, the usrCMoldPart is within the Ext
 

int1 is part of PX.Objects.CS, I am not sure why it was erroring there. You can probably convert the DAC to an extension and add using PX.Objects.CS to resolve that part of the error

josiahl64 wrote:

The bql field is what you should be using in your query, the usrCMoldPart is within the Ext
 

int1 is part of PX.Objects.CS, I am not sure why it was erroring there. You can probably convert the DAC to an extension and add using PX.Objects.CS to resolve that part of the error

I’ll have to hit the wiki because I’ve never converted to an extension before… thanks Josiah!