Skip to main content
Question

Possible to dynamically make hidden field visible?


Forum|alt.badge.img

I have a field hidden via Low Code… do I need to set a condition and/or workflow to dynamically make it visible?

11 replies

Samvel Petrosov
Jr Varsity II
Forum|alt.badge.img+5

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.
 

 


Forum|alt.badge.img
  • Author
  • Freshman II
  • 166 replies
  • March 20, 2025
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.

 


Samvel Petrosov
Jr Varsity II
Forum|alt.badge.img+5
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

 


Forum|alt.badge.img
  • Author
  • Freshman II
  • 166 replies
  • March 20, 2025
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>>))]


Naveen Boga
Captain II
Forum|alt.badge.img+19
  • Captain II
  • 3404 replies
  • March 21, 2025

@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?")]


Forum|alt.badge.img
  • Author
  • Freshman II
  • 166 replies
  • March 21, 2025
Naveen Boga wrote:

@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.

 


Naveen Boga
Captain II
Forum|alt.badge.img+19
  • Captain II
  • 3404 replies
  • March 21, 2025

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


Forum|alt.badge.img
  • Author
  • Freshman II
  • 166 replies
  • March 21, 2025
Naveen Boga wrote:

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

Absolutely, thank you Naveen!

 


Naveen Boga
Captain II
Forum|alt.badge.img+19
  • Captain II
  • 3404 replies
  • March 21, 2025

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

 


Forum|alt.badge.img
  • Author
  • Freshman II
  • 166 replies
  • March 21, 2025
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…

 


Naveen Boga
Captain II
Forum|alt.badge.img+19
  • Captain II
  • 3404 replies
  • March 21, 2025

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


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings