Acuminator | specific code analysis tools and an extension for Visual

by Acumatica C# Version: v3.2.0 License: GPL-3.0

X-Ray Key Features Code Snippets Community Discussions(6)Vulnerabilities Install Support

kandi X-RAY | Acuminator Summary

Acuminator is a C# library typically used in Plugin, Visual Studio Code applications. Acuminator has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

Acuminator is a Visual Studio extension that simplifies development with Acumatica Framework. Acuminator provides the following functionality to boost developer productivity:.

Support

Quality

Security

License

Reuse

Support

Acuminator has a low active ecosystem.

It has 27 star(s) with 5 fork(s). There are 17 watchers for this library.

It had no major release in the last 6 months.

There are 18 open issues and 29 have been closed. On average issues are closed in 35 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of Acuminator is v3.2.0

Quality

Acuminator has 0 bugs and 0 code smells.

Security

Acuminator has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

Acuminator code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

Acuminator is licensed under the GPL-3.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

Acuminator releases are not available. You will need to build from source code and install.

It has 30 lines of code, 0 functions and 1258 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Acuminator

Get all kandi verified functions for this library.

Acuminator Key Features

No Key Features are available at this moment for Acuminator.

Acuminator Examples and Code Snippets

No Code Snippets are available at this moment for Acuminator.

Community Discussions

Trending Discussions on Acuminator

Add buttons to Grid in Acumatica

Error While Creating Action in Sales Quotes Screen CR304500

Prepare Payments page not showing PayDate after adding a filter

In Acumatica, why is my JournalEntry extension delegate not firing?

How to add a New Action to the mobile App

Acumatica/Acuminator Error PX1016 - looking for more information regarding this Acuminator error

QUESTION

Add buttons to Grid in Acumatica

Asked 2021-Aug-31 at 13:23

Good day

I want to add two new buttons to the Payment Instructions Grid on the Vendors page. I would like help to show the new buttons on the grid.

C#:

...

ANSWER

Answered 2021-Aug-31 at 13:23

Since no version was specified, my solution was done against 2021 R1.

To add your actions to the grid you perform the following steps:

Open your customization package
Add your screen [AP303000]
Open the added screen
Find your action (DataSource --> Toolbar --> Form-Specific --> Approve Payment Method)
Set the following Properties:

DependsOnGrid: grdPaymentDetails (this is the id of the grid control you are adding it to)
Visible: False (this hides it from the top of the screen)

Save
Find the grid you want to add the action to (Tab --> Payment --> Form --> [2nd] Column --> Group --> Grid: PaymentDetails)
Add Control to Grid (Add Controls --> Click and Drag BUTTON onto Grid:PaymentDetails)
Select new button ([Grid: PaymentDetails] --> ActionBar-CustomItems --> ToolBarButton
Set the following Properties

AutoCallBack --> Command: ApprovePaymentMethod (this is the action name in code)
AutoCallBack --> Target: ds (this is the datasource for the action)
Text: Approve Payment Method (This is the text shown on the button)

Save

At this point you would normally be able to repeat steps 4-11 for RejectPaymentMethod then publish and see the actions moved into the grid. For this particular situation there is a catch. The grid you want to add them to has the SkinID of Attributes which doesn't support the action toolbar. You need to override this property with the following steps:

Select the target grid (Tab --> Payment --> Form --> [2nd] Column --> Group --> Grid: PaymentDetails)
Update the following Property:

SkinID: Details

Save

Now you can publish and see the action shown as desired. Note details will show the standard button set, so you'll likely want to remove those with the following steps

Select the target grid (Tab --> Payment --> Form --> [2nd] Column --> Group --> Grid: PaymentDetails)
Set the following Properties:

ActionBar --> Actions --> AddNew --> ToolBarVisible: false
ActionBar --> Actions --> AdjustColumn --> ToolBarVisible: false
ActionBar --> Actions --> Delete --> ToolBarVisible: false
ActionBar --> Actions --> ExportExcel --> ToolBarVisible: false
ActionBar --> Actions --> Refresh --> ToolBarVisible: false

At this point when you publish your actions will be on the grid (this is assuming you've repeated steps 4-11 for RejectPaymentMethod.)

Source https://stackoverflow.com/questions/68996115

QUESTION

Error While Creating Action in Sales Quotes Screen CR304500

Asked 2021-Apr-12 at 15:09

I have created an Action in Sales Quotes Screen to create my "Forecast Document" (Customize Screen) and get the Forecast Document Nbr back into the Sales Quote Screen in the field "Forecast". Though the below code is working absolutely fine in other modules Like SO, PO and ARInvoice. As the Error says "Forecast document cannot be found in the system" which is not so, I can see the same document in the Forecast Document Screen. Following is my code:

...

ANSWER

Answered 2021-Apr-12 at 15:09

Error document 'X' cannot be found in the system often occurs because the selector attribute can't get the record.

The first troubleshooting step is to check if the record exists in the database.

If the selector filters out the target record you will get this error. You can remove the selector attribute filter (joins and where clauses) to check if this is the root cause of the error.

Source https://stackoverflow.com/questions/67020882

QUESTION

Prepare Payments page not showing PayDate after adding a filter

Asked 2021-Jan-11 at 23:29

I added a new filter to Prepare payment(AP503000). The filter works as expected.

After testing I realized that the Pay Date(APInvoice.PayDate) doesn't show data in the grid How can I make the paydate data show?

I see that a lot of the data comes from APAdjust and the data missing comes from APInvoice.

CODE:

...

ANSWER

Answered 2021-Jan-11 at 23:29

You're yielding an APADjust record when your view is a join between the two tables APAdjust & APInvoice. Try something like this:

Source https://stackoverflow.com/questions/65666437

QUESTION

In Acumatica, why is my JournalEntry extension delegate not firing?

Asked 2021-Jan-02 at 06:51

In an Acumatica customization, I want to check journal entries after they are posted to see if they are being posted to a specific branch so I can create entries for another Tenant.

I am using the JournalEntry graph and creating a delegate on the ReleaseBatch method.

I know the extension is being hit because anytime I click anything on the Journal Entry screen, breakpoint on private bool testingExtensionIsActive = true; gets hit. In order to get the code to compile I had to put the ReleaseBatchDelegate baseMethod before the bool unholdBatch = false parameter. Optional parameters have to go at the end of the signature. Normally the baseMethod goes at the end of the signature for the other delegates I have created.

I also tried another delegate just to see if I could get ANYTHING to work. The second delegate in my code is for the PostGraph graph. It has a simple signature so I thought that would rule out the issue I just describe above with the optional paramater.

I cannot hit the breakpoint set on string joe = "joe"; in either delegate.

...

ANSWER

Answered 2020-Dec-31 at 15:18

I left out [PXOverride]. How embarrassing.

This one works now. The ReleaseBatch delegate doesn't work but that is due to a different issue.

Source https://stackoverflow.com/questions/65515204

QUESTION

How to add a New Action to the mobile App

Asked 2020-Sep-11 at 07:38

Good day

Build 20.107.0026

I have created a New Action and want to add it to my Mobile app. Is it possible to add a custom action to a mobile screen? I have created the below action in the Appointment screen(FS300200)

...

ANSWER

Answered 2020-Sep-10 at 15:32

The short answer is YES! The long answer depends in part on what version of Acumatica you are using. For the purpose of this answer, I'll assume you are in 2019R2 and already know how to add or edit a Mobile App screen in Acumatica. If not, the training guides referenced below should give you all the detailed information you need to accomplish your goal.

Manipulating the Mobile App screens/actions is relatively easy if the screen/action works in the browser interface. The T410 course material explains how to add an action in 2019R2. I don't work with Field Services, so I'll have to explain more generically as per the training guide.

First you must either add or edit the screen in the Mobile Application section of the Customization Project. (In your case, you want to Update the existing screen.) This will create a section of code in the customization project that looks like this:

As you can see, the original screen definition in the mobile app is shown on the right, and you will be updating the screen to add your action. You will need to add the appropriate container (not shown in your question) and then the action within that container.

To continue the answer, let's switch to the training guide example on page 12 of the T410 course updating the SO303000 screen. You can compare to your screen to see what needs to be changed.

Source https://stackoverflow.com/questions/63831494

QUESTION

Acumatica/Acuminator Error PX1016 - looking for more information regarding this Acuminator error

Asked 2020-Jul-23 at 15:24

Good day

I recently updated my Acuminator and got the error below. I see there is a reduced performance if I don't add this function to my extensions. I was hoping some can explain this a bit better as I do see performance issues where I have a lot(20+) customizations running on one site.

Error PX1016 A graph extension must include a public static IsActive method with the bool return type. Extensions which are constantly active reduce performance. Suppress the error if you need the graph extension to be constantly active.

Only reference I found of this was here: https://gitmemory.com/SENya1990

An example of the code described here would be appreciated

...

ANSWER

Answered 2020-Jul-23 at 14:42

The most common case is when you need to use your GraphExtension only under the specific feature

Source https://stackoverflow.com/questions/63050531

Community Discussions, Code Snippets contain sources that include Stack Exchange Network