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"
Related
I started using Acumatica ERP framework to create a sample application. I follow the steps provided in training document. By following the steps i added a ListView maintenance page.
The newly created page has PX.DataSource control created by acumatica framework. But this control has one error message with it i.e. "Error Rending Control - usrCaption". I attached the screenshot of this error.
I reinstalled framework many time but still same issue occurred to me. I opened my project on other machines and it's working fine. and also projects created on other machines that are working fine on source machine also giving same error on my machine.
Why Acumatica ERP PX.DataSource give rendering error at design view?
Usually this occurs because the template are lagging behind in terms of maintenance and aren't 100% compatible with all possible Visual Studio deployment (especially the latest versions).
The templates are very rarely used and since the Customization Project Editor has all the same features and more this is the one most users are using and the focus is put on maintaining this one before the Visual Studio templates.
It's unfortunate that the T100 training documents focus on these. Support regarding the templates is always originating from T100 training since they aren't very useful besides that. I would prefer the training direct new user to the Customization Project Editor instead because as far as I know it is what everybody uses and the only one that is always up to date.
I have a local instance of Acumatica 2018 R2 that I am using for development and when I try to edit a Customization Project it is not pulling in the specific project and ID.
Local instance of the Custom Project editor
Where it says "Project" in the top left, it should say "Test5".
Here is how the editor should look:
Production Instance Custom Project Editor
I believe that I've configured my IIS setting correctly but I can't get it to perform correctly.
I've seen that happen before. It appears to be an Ajax glitch. When the customization project editor opens it displays Project as a placeholder first. Then an Ajax call fetch the proper project name to replace the template placeholder text.
There isn't much to do to resolve this issue. I suggest using a different web browser (Chrome seems to handle Ajax more reliably) and possibly issuing an IISReset command on the web server or if you don't have access to server a restart application from the apply updates page.
There's something fishy with the way the projects are being exported. Say I have two companies, a production and test. I move customisation projects between them. From testing, I wrote a new screen MA.20.20.20. And under custom files, the ASP files are listed as follows.
Once working I exported this project, got the ZIP file and then imported into production. For some reason, my customised screen MA.20.20.20 is missing from the list in the production. It's just blank ! The ASP files are still listed though and I checked ZIP project. The physical files are still in there.
So what's am I doing wrong here?
TIA
It sounds like you are referring to two different entries in the project. Your files are the pages in the pages directory while it seems like you also have screen modifications to your custom page files which I assume under customized screens would require a site map entry.
Are you including your sitemap entries in your customization project?
It seems like a little glitch in Acumatica. Publishing anyway ignoring this would solve the problem.
This is just a permissions issue. Make sure your role has access to that particular screen. It's a bit strange as I would expect the screen to show within the Customization Project for the administrator but apparently it doesn't. I had faced a similar problem where in my local instance access permissions was Not Set for any roles and thus I could see the screen. But in production one of the roles had the access Revoked for the screen and thus even the admin couldn't see the screen even within the Customization Project.
I use VS2010 on Server 2008 R2 with Sharepoint 2010 Foundation.
I have created a custom master page following instructions from here: http://msdn.microsoft.com/en-us/library/gg447066.aspx (activating my custom page as feature), and was delighted with the results. But as soon as I changed the images and attempted to deploy them through VS2010, I noticed that my changes were not showing in the page (which was still showing the old images).
Useful observations:
It's a Sandboxed solution.
I checked that wsp is built with the new images, and so it was.
When I retract my solution, I also go to Master Page Gallery, and
delete my custom master page from there to make sure I start from
scratch. No difference.
My SP Designer does not give me an option to "revert to site
definition".
My "Look and Feel" section in central admin does not offer a
"reset to site definition" option.
Checking "CustomizedPageStatus" property of the SPFile for my master page shows that it's set to "none", and indeed, calling RevertContentStream throws an exception. This indicates it may not necessarily be the unghosting issue.
Does anybody know where my images get deployed to, and what the cause of this problem may be? The "Deployment Location" property does not lead to the correct location (in fact, I can't even see my Feature's folder). Could it be something to do with the way variables in the path - {SharePointRoot}\Template\Features{FeatureName}\StyleLibrary\Branding101\Images\ - are parsed?
I am new to Sharepoint, so all and any help would be much appreciated.
Since this is a Sandboxed solution, everything gets stored in the content database, accessible through SharePoint Designer 2010. In SP Designer, open the site you are working on, then look under "All Files" in Site Objects: that's where I found my masterpages, images, etc.
Deployment paths (displayed in module properties in VS2010) are just red herring, as no deployment to the file system itself takes place. Hope this helps somebody else!
I am developing publishing site. I have some layouts that are pre-populated with web parts and have a problem when I need to make some change on the layout.
Deployment succeeds but I still see old version. If make I change in SP Designer it is reflected OK but not if the change is done by the feature that is being deployed.
It looks like after I deploy particular layout any site collection in that web application will have the first version.
I have tried deleting complete site, all the pages, layouts and nothing happens, after deployment I still see old layout.
Current solution for this problem was that I take new virtual image and start with clean machine.
Real problem is how to solve this on clients installation without reverting to clean machine. There will be some bug fixes and I will have to send new WSP file with some changes in layout.
Is there any way to force SharePoint to use newly deployed layout and not some old Unghosted version?
If the layouts are without web parts I don't have this problem.
Update
I am using default "Publishing Portal" and deploying layouts using features. For development I am using VSeWSS 1.3.
tried in SharePoint designer to detach page from layout and attach it again but still no results.
Since you are using VSeWSS, you can execute your own code upon feature activation. So try writing an SPFeatureReceiver that will call SPWeb.RevertAllDocumentContentStreams() to reghost directly after feature activation on the web(s) in question.
If this doesn't work, then the problem isn't about ghosting, maybe it's about Orphans then. But try this first.
If it's a feature that you are deploying you have do deactivate the feature and activate it after deployment again. And don't forget to do an IISRESET or an AppPool recycle.
If your new site collection has the first version of the layout make sure that it is really your new feature version that you are activating.
Try to reject your solution first and add the new one after that.
Are you using Site Definitons or Site Templates? If you are using either of these it may not update after initial provisioning.
Try completely retracting and deleting the solution from central admin, resetting AppPools and then redeploying the solution.
Make sure your element manifest for your feature specifies that existing files should be overwritten.
Looks like some folks have had problems with layouts too...
See http://msdn.microsoft.com/en-us/library/ms459213.aspx
If you are developing new sitedefinition, you can attach your new layout in the onet.xml file by using the property, i hope it will help you
-->