Skip to main content

Acumatica Community Webinar - Demystifying No Code Customizations - Wed, May 22, 2024 - Recording

This webinar will focus on some of the do’s and don’ts of publishing, creating actions and conditions, adding new fields, modifying workflows, combining customizations and business events, and understanding the makeup of a screen. Tips and tricks will be sprinkled throughout.

Presented by David Gross @dgross 

About David: I have been an Acumatica business consultant and implementation specialist since 2018. My areas of expertise include Distribution, Manufacturing, Field Service, CRM, and Ecommerce to name a few. I can create complicated GI’s and Reports (ARM and regular) and I am able to guide my clients through complicated needs assessment and create the solutions required to satisfy those business needs. My interest in customizations was borne out of necessity and sustained by curiosity. The more I am able to do without contracting a developer the better, and I am happy to share what I have learned (through much trial and error) so others can feel less intimidated and more empowered.

Please Note: As with any community content, nobody can be held responsible for any negative consequences resulting out of information derived from this community. Please be sure to test any ideas from this webinar in a non-production environment.

 

14 replies

D
Rank
Userlevel 4
Badge

I never got to my Do’s and Don’ts so I thought I would add them here.

  1. Always export the custom you are going to work on.  If something happens and the customization is corrupted somehow you can follow these steps to recover.
    1. Take a screenshot of the entire customizations screen (so you know which ones were published and in what order/level)
    2. Unpublish all customizations
    3. Delete the corrupted customization.
    4. Save
    5. Import the previous version you exported from your download folder.
    6. Publish all the customizations that were previously published. 
  2. NEVER delete a published customization
  3. Custom screens (not made by/standard Acumatica) should be in one customization only.  It’s ok for Acumatica screens to be in multiple customizations.
  4. Use the Description to chronicle what you have done in the customization project. 
Chris Hackett
Rank
Userlevel 7
Badge

Thank you for sharing this with the community @dgross!

Chris ~ Let us know how we're doing: https://forms.office.com/r/xmJUdZ1QE5 - A member helped you, please *Like* their post. A member provided an answer to your question, please mark it as *Best Answer*.
ejmillar
Rank
Userlevel 5
Badge +1

Hi @dgross,

Many thanks for the webinar. I found it very useful and I’m looking forward to the next one.

Cheers,

Ewan.

 

 

Ewan ~ Rubech IT ~ Please remember to "Mark Best Answer" to help those who are facing the same problem.~
angusf
Rank
Userlevel 1

I enjoyed the webinar. It could easily be a series - there’s such a lot to learn about Acumatica best practices and although there is lots (maybe too much) existing documentation it is often too generic and doesn’t get to the heart of the issues with practical steps you can take to make Acumatica better.

Several of the throwaway bits of the webinar were worthy of whole sections!

Please consider doing some more. 

 

Angus 

 

D
Rank
Userlevel 4
Badge

@ejmillar @angusf 

Thanks for the feedback.  Chris and I just settled on doing another follow up later this month and potentially another one next...we’ll see.

 

-David

D
Rank
Userlevel 5
Badge +3

For the next session, modifying the selector for a detail line on a form like sales orders.

jlian37
Rank
Userlevel 2
Badge

Thanks for taking the time to share your knowledge, @dgross.  Like the others, I have learned much from this short session and look forward to the next one.

Quick questions - Is it possible to limit a customization to a group of users or a specific user?   Or do they always apply to everyone in the same instance/tenant?

John Lian
D
Rank
Userlevel 4
Badge

@jlian37 You can set a condition and use that condition to limit the workflow to an owner or a workgroup as long as those fields are available on the screen.  Generally speaking, though, you would customize and then control via access rights or restriction groups. 

jlian37
Rank
Userlevel 2
Badge

@jlian37 You can set a condition and use that condition to limit the workflow to an owner or a workgroup as long as those fields are available on the screen.  Generally speaking, though, you would customize and then control via access rights or restriction groups. 

Thanks, but sorry to be dense as I am new to Acumatica - let’s say I have a customization project that hides some fields and makes some fields conditionally required.   But I only want that project to apply certain users/groups, not all.  How exactly would I accomplish that?   Not sure if what you suggested would work.

John Lian
D
Rank
Userlevel 4
Badge

@jlian37 

You cannot apply a customization to certain users/groups.  Learn about access rights.

 

-David

jlian37
Rank
Userlevel 2
Badge

Will do, thanks.

John Lian
annetrockman27
Rank
Badge

Is there a recording of part 2 that happened on June 27? I was registered but could not attend the meeting.

Ignore this… I found the link! 

 

 

Anne Trockman
Chris Hackett
Rank
Userlevel 7
Badge

Hi @annetrockman27  - All webcasts are recorded and posted in the Community Library.

Chris ~ Let us know how we're doing: https://forms.office.com/r/xmJUdZ1QE5 - A member helped you, please *Like* their post. A member provided an answer to your question, please mark it as *Best Answer*.
jamest
Rank
Userlevel 3
Badge

@dgross 

How granular do you go when creating a customization project? For example, do you create a project for every Report or GI you create or change? Or do you have one Project for all custom reports and GIs? Thanks!

Reply


Terms & ConditionsCookie settings