Use a browser debugger Inspect Element feature to look up the HTML control names and CSS class of the target controls.For example here I looked up HTML control ‘label’ : Then modify theme file located in ‘\YourWebsite\\App_Themes\Default\00_Controls.css’ to change the CSS style. Here I changed HTML label controls color to red by adding this style:label { color: rgba(255, 0, 0, 1);} The About box dialog uses a span HTML control instead of a label.The control has a CSS class labelH we can target but it also has inline style which will override the CSS style:<span class="labelH" id="ctl00_usrCaption_pnlAbout_lblAcumatica" style="color:#4E576A;font-size: 22px; font-weight: bold">Acumatica 2020 R2</span> To have CSS class applied instead of the inline style color you need to add CSS important keyword:.labelH { color: rgba(255, 0, 0, 1) !important;}Style properties marked important will be applied even if another style is trying to override it: ForeColor property works at ASP l
You can try calling the base method first, maybe it’s reverting the visibility changes:protected void SOLine_RowSelected(PXCache cache, PXRowSelectedEventArgs e, PXRowSelected del){ if (del != null) { del(cache, e); } var row = (SOLine)e.Row; if(row != null) { PXUIFieldAttribute.SetVisible<Objects.SO.SOLineExt.usrCoutUnitEntrp> (cache,row,false); PXUIFieldAttribute.SetVisible<Objects.SO.SOLineExt.usrStkDispEntrp> (cache,row,false); }} If using a recent Acumatica version, it’s possible the new workflow feature reverts your change too:https://www.acumatica.com/media/2020/07/2020-Workflow-Engine-final.pdf
You need to use the Type identifier which starts with a lowercase ‘u’:PXUIFieldAttribute.SetVisible<Objects.SO.SOLineExt.usrCoutUnitEntrp> (cache,row,false);PXUIFieldAttribute.SetVisible<Objects.SO.SOLineExt.usrStkDispEntrp> (cache,row,false);Instead of the DAC field Value identifier which start with an uppercase ‘U’:PXUIFieldAttribute.SetVisible<Objects.SO.SOLineExt.UsrCoutUnitEntrp> (cache,row,false);PXUIFieldAttribute.SetVisible<Objects.SO.SOLineExt.UsrStkDispEntrp> (cache,row,false);
The error suggests the code you tried is not equivalent to the solution I suggested.Notice that the field is named ‘usrStkDispEntrp’ and starts with lowercase ‘u’ in my answer.PXUIFieldAttribute.SetVisible<Objects.SO.SOLineExt.usrStkDispEntrp> In your error message, the error is on a different field 'UsrCoutUnitEntrp' and it starts with a uppercase letter ‘U’.
‘rowExtension’ is a variable of the type ‘Objects.SO.SOLineExt’Generic parameter like the one for SetVisible method requires a Type identifier:PXUIFieldAttribute.SetVisible<Type>In your example that should be:PXUIFieldAttribute.SetVisible<Objects.SO.SOLineExt.usrStkDispEntrp>
Moving the source code to an extension library (DLL) would make it inaccessible in its original form.Reference: Code in DAC and Code items Code in an Extension Library Intellectual property protection: No—the source code is open in the deployment package Yes—the source code is not provided in the deployment package https://help-2020r1.acumatica.com/Wiki/ShowWiki.aspx?pageid=6eef9fa0-ab15-4c9f-8376-3c4f1b4118a4
Yes it is possible. In Acumatica files are attached to Screens. You still need to link files in Wiki.After creating a custom screen upload files in it. By default there will be a toolbar ‘Files’ action button to attach files. Screen ‘Search in Files’ SM202520 can display file list filtered by Screen ID: This page graph is in PX.Data assembly, I attached the code with this reply.
Make all columns the same size in the form container and it should align.Size of the column is the size of the largest element it contains. You can use the standard size described here:https://asiablog.acumatica.com/2016/04/extend-change-field-size.html Standard sizes for Controls and Labels:XXS (40px) XS (70px) S (100px) SM (150px) M (200px) XM (250px) L (300px) XL (350px) XXL (400px)For special cases you can use CSS with the Style property to set a control position manually:<px:PXLabel ID="lblCustomerIDH" runat="server" style="z-index:107;position:absolute;left:239px; top:69px; margin-bottom: 10px;"></px:PXLabel>
The bug is fixed in those versions which will be released soon:2019 R1 Update 22 2019 R2 Update 15 2020 R1 Update 13 2020 R2 Update 3 2021 R1 Beta
The sort needs to happen on the database with BQL/SQL for performance reason. If items need different pick priority based on the warehouse they are stocked then you need to store different priorities in database.How many depends on your business rules. If each warehouse has a different priority then a priority per warehouse is required. If they are not all different and can be regrouped by warehouse types you can cut down on the amount of data needed.
As a workaround for self-hosted Acumatica instance. Modify web server file ‘Web.Config’ at the root of your Acumatica instance folder. Add this key in appSettings section:<appSettings> ... <add key="aspnet:DisableAppPathModifier" value="false" /></appSettings> For instance hosted on Acumatica SaaS service please open a support case with Acumatica.The issue occurs with .Net version 4.8.4250. It works up to version 4.8.3752 without this workaround.
It’s a known issue currently under investigation.
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.