NetTool | macOS menubar tool | Menu library

Here's the email I got from Acumatica Support:

We've investigated the issue and found that it is caused by compatibility with new version of .Net Framework.

You can find more details here:

https://community.acumatica.com/customization-and-development-72/known-issue-after-an-upgrade-to-net-framework-version-4-8-4250-users-were-unable-to-publish-a-customization-project-from-the-customization-project-editor-3854

This issue is fixed in the following versions:

• 2019 R1 Update 22
• 2019 R2 Update 15
• 2020 R1 Update 13
• 2020 R2 Update 3

As a workaround you can set the following flag to false in the web.config of the site (appSettings section):

Full Credit: Dmitry Naumov

You will need a state or add it to this state to configure the server to use HTTP_PROXY before running these packages. See the following document on configuration of this:

https://www.shellhacks.com/linux-proxy-server-settings-set-proxy-command-line

Also see this article from Salt: https://docs.saltstack.com/en/latest/ref/states/all/salt.states.proxy.html

I don't think there is a way to avoid this right now. The upgrade process does not guarantee that your published extensions will be loaded and can cause errors like these.

Some customizations, specially the ones done inside Acumatica may work during the upgrade with no issues, but it is common to get some kind of exception for customizations with an external DLL.

The upgrade process recommendation is basically to avoid getting and error and then going back and having to unpublish anyway. It's better to always unpublish your customization first, then perform the upgrade and finally republish again.

OK, my conversation with Fernando was helpful. Here's what I discovered, and here's what worked:

The fact that there are two different ways of selecting "Branch" in the Fields is significant.

One shows up in the "Document Details" PopUp

And one shows up in the Financial Settings -> Financial Information PopUp:

As it turns out BOTH are needed. But they can't both belong to the SalesOrder Entity -- that's not allowed.

So, I extended the SalesOrder Entity with the Financial Settings "Branch"

And, I extended the SalesOrderDetail Entity with the DocumentDetails "Branch"

And then I could do this and it was accepted:

It looks strange, I don't see any related fields with "Invoice Date" display name, which may cause an issue. I faced similar strange issues due to IIS data caching.

I would recommend do the following:

• Restart IIS
• Remove temp ASP.NET files which are located somewhere here C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files
• Remove temp Customization files

Then to be sure the problem is not in your customization

• Rename your custom field from "Invoice Date" to "Invoice Date 1" for example
• Publish your customization again
• Try your steps again and verify an error message if it still exists - which display name do you see, "Invoice Date" or "Invoice Date 1"?

If you want to fix this derivation for macOS, the way to do it is to fork nixpkgs on github and then from your local clone:

I've only used scrapy-splash a handful of times, but heavily rely on scrapy. My guess is that you're using a splash instance from scrapinghub. I think it's because of the ip that's actually being used to make the request.

One example I have is trying to scrape google shopping. Google traces the ip back to the origin. So regardless of my ip pool being located in the US. Some ips where tracing back to other countries and returning results for that county. Say we have the below code.

I found my issue. I had a PXSelector in my graph that shouldn’t have been there, and there was an issue with its join. I removed it and now am ok.

Salt's states (sls files) go in /srv/salt/ unless you've modified the file_roots option in your master config file.

So if you place your file in /srv/salt/nettools.sls you should be able to run the following command: