I have an Acumatica customization that uses a third-party (Smartsheet) API reference. This works fine in a development environment - even re-publishing the customization project - but when it's packaged up and deployed on another instance, I get the following error:
Not sure if anyone would have any suggestions on what might possibly cause this error, but I just thought I'd check...
Thanks
The answer is that you have to include all dependent dlls for the third party API in the Acumatica Customization project's 'Files' section, even though they're compiled as references in the Acumatica customization project's Visual Studio project.
Thanks to Brian Stevens (above) for his answer and making me realize this...
Related
I’m experiencing an issue with customization projects in Acumatica 2017 R2 Build 17.203.0029.
Specifically, custom screens, while in my project XML, are not visible within the customization project browser nor can they be navigated to once published (which occurs without error). This only occurs on my staging server. Everything works fine in my local dev environment and even on a different instance of Acumatica. My local dev environment matches the staging server in every possible way (Acumatica version, other packages, etc.)
Older versions of the same customization project have been published before and did not exhibit this behavior. It’s only after I replaced the project with newer version of the same project that I encounter the missing custom screen issue.
As shown in the screenshot below, remnants of the custom screens are present in the Customized Screens window. And the ASPX files are present and shown in the Custom Files window.
Screenshot of missing custom screen data
When I compare the “Edit Project Items” objects between the staging the server and my local dev version, they appear the same.
It it possible that the internal customization or sitemap tables on the staging server have inconsistent data? Is there anyway to rebuild them?
The solution appears related to the users roles config. I had not assigned access rights to the custom forms. Doing so solved the issue. The custom screens are now accessible by direct URL and are shown in the customization project browser. Maybe this will help someone else.
I had this same issue when trying to Deploy the customization to another instance.
To fix it I had to go to the site manager and change the URL of the new page
from: "/Pages/SO/CustomName"
to: "~/Pages/SO/CustomName"
Dynamics CRM 2011 on premise.
We have had a plugin registered for a few months. It was referenced by a solutions in two organisations and I could see it in Solution > Components > Plug-in Assemblies in each organisation.
Yesterday I noticed it was not visible in this view. The Plugin Registration Tool shows it still installed.
I unregistered it using the Plugin Registration Tool and then registered it again but it still isn't visible in the solution that references it in either organisation.
We get a "Could not load file or assembly" exception when the plugin is called.
How can I investigate this?
Registering a plugin doesn't put it in a solution. You'll have to add it back manually to whatever solution(s) you want.
Go to Customizations > Solutions > Open your solution you want the plugin added > Plug-in Assembly > Add Existing. If the dll doesn't show up there, you either didn't register it at all, or registered it for a different org
Go to Customization > Customize the System > Plug-in Assemblies
When you deployed, it might be installed in default solution. You can always add it back to your Solution as #Daryl said.
Ok, I'm not sure why, but it seems to be working again.
I removed all trace of the plugin from both servers and from the orgs and solutions and then added it back and now it seems to be ok.
Is annoying because I don't think I learnt anything and it used a lot of time.
Thanks for your help.
Does anyone here know what could cause a new feature to not show up in the SharePoint UI?
The solution it is part of has been correctly deployed to the GAC and shows up in the central administration list of deployed farm solutions, the feature appears in the FEATURES folder of the 14 hive, yet the feature itself does not appear in the features list for the site collection, either in the UI or in PowerShell using Get-SPFeature.
Yes, the feature is correctly scoped, and no, it is not hidden. :)
Any thoughts or pointers would be very welcome!
Answer supplied on sharepoint.stackexchange.com, with thanks to Simon Doy. https://sharepoint.stackexchange.com/questions/73871/sharepoint-2010-feature-not-appearing-in-ui
Somehow, something had gone wrong with the installation of the feature, and neither the UI nor commands like Get-SPFeature revealed its existence, although the Install-SPFeature -ScanForFeatures command emboldened below displayed the missing feature.
"Check that the feature has been installed. For example, if you are
performing Update-SPSolution and a new feature has been added between
solution deployments then the feature is not installed by default.
To check do the following:-
Run SharePoint 2010 Management Shell from one of the SharePoint
servers Type Install-SPFeature -ScanForFeatures This will show you any
features that are available in the SharePoint Root but have not been
installed. You can install any missing features using the command :-
Install-SPFeature -AllExistingFeatures
See the following TechNet
Article for more information.
http://technet.microsoft.com/en-us/library/ff607825(v=office.14).aspx"
Look in central admin to see what site collection the feature is deployed to. Make sure in that site collection the feature is turned on.
Also, check the deploy job status to see if it actually finished.
Is there a on install event receiver? If it errors out, the feature will not finish installing even after the DLL is copied.
We have a very large solution project for our MVC structure where I work. I am trying to filter my solution explorer down to only relevant files with a custom filter. Microsoft has an article on making a custom filter here, but when I try to build the source code they give it says one of the .NET Framework namespaces is not available (I have already reinstalled .NET). The namespace that won't resolve is: System.ComponentModel.Composition. I am hoping fixing this will allow me correctly build a filter (there are 5 errors in the project total).
I definitely have the 2012 SDK installed (you won't make it far in the tutorial without it).
The Funnel extension may be what you're looking for:
Decrease solution loading and re-compilation times dramatically by filtering projects not relevant for the current task.
The extension loads just the projects defined in filters (load filters must be defined before using them).
You've to add reference to "System.ComponentModel.Composition" assembly. This reference is in framework 4.0.
If you've problem referencing or finding this assembly, refer to this answer:
https://stackoverflow.com/a/6310236/2617201
I am trying to use a Visual Webpart in a sandbox solution. However every I deploy it: it gives me the following error:
Error 1 The deployment type "TemplateFile" of file "VisualWebPart1UserControl.ascx" in Project Item "VisualWebPart1" is not compatible with a Feature in a Sandboxed Solution.
I did some research and found out that Visual WP is not supported in Sandbox solutions. Is there anyway I can have Visual WP in a sandbox solution?
And is there any specific reason as to why Visual WP is not really supported in Sandbox solution.
Use VS Sharepoint Power Tools. It has Visual Web Part item template for sandbox solutions.
http://visualstudiogallery.msdn.microsoft.com/8e602a8c-6714-4549-9e95-f3700344b0d9/
Please follow this link
Restrictions on Sand boxed Solutions in SharePoint 2010
http://msdn.microsoft.com/en-us/library/gg615454.aspx)
it will provide you the detaisl about the limitation of Sandboxed solution.
RoManiac is correct, you can not deploy visual web part in Sanboxed solution as it contains user control.
Mark as answer if it helps you.
You can deploy a solution directly onto your SharePoint Server farm, or you can deploy the solution into a sandbox. A sandbox is a restricted execution environment that enables programs to access only certain resources, and that keeps problems that occur in the sandbox from affecting the rest of the server environment. Solutions that you deploy into a sandbox, which are known as sandboxed solutions, cannot use certain computer and network resources, and cannot access content outside the site collection they are deployed in.
Normally, a Visual Web Part cannot be sandboxed, as it needs to work outside the sandbox in order to load the underlying user control for the Visual Web Part.
This is how to have a Visual WP in a sandbox solution:
http://msdn.microsoft.com/en-us/office365trainingcourse_lab_2_1_topic3.aspx