I have added Manage subfolder to Distribution->Sales Order->Work Area
The problem is that when I am adding pages to that subfolder I am not able to include that subfolder in the Customization's Site Map part and as a result the page is not being added to the testing system.
The version of the Acumatica ERP is 17.204.0019.
I have not this issue in the 6.10 versions.
Set a ScreenID to your "manage" folder and put the default value "~/Frames/Default.aspx" in URL. This is a known bug in some versions
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"
I have a site created in SharePoint Online that I have applied a custom css file through the Master Page - Alternate CSS. The css file is saved in the Style Library, it is checked in and published as a major version. I am using the default master page and it is also checked in. As an admin I can see the CSS changes on the site but as another user that has read access I cannot see the CSS changes. The read only users can see the top level site. I have checked the site features at site collection and site and all publishing features are active. What setting could I be missing that would cause this CSS not to show? The CSS changes are specifically to hide some buttons on the app launcher just for this site.
Thanks for your help.
CSS on Master page page will be shown to all authenticated users if CSS(style library) and master page both are checked in and published as major version.
also try removing cache and so proper revision of CSS and JS file before deployment.
also check console of browser for non accessible file :)
We set up the SharePoint 12 hive folder for a custom theme with a new xml entry and folder.
Is everything required for a custom theme living in the theme folder? I'm asking because we are seeing CSS files that appear to be dynamically named rendered on SharePoint pages in the folder that are not actually in the folder.
Will we have to use SPD and custom site changes to get a custom theme to work?
I've got a designer working only in the theme folder, but he is seeing rendered css that he can't get to. He is not using SPD
That 1011-65001 squence file is found nowhere? what is that an where can I find it. Any way to have my custom theme all hard fixed name css files in that folder without using SPD?
/_themes/MYNEWFOLDER/MYNEWTHEME1011-65001.css?rev=12%2E0%2E0%2E6421
===
Update: I just realzed that css is creatd when I apply the theme and so it's in my _themes site folder. But now, when I attempt to re-apply the theme, that was working before, now i get a write error on _themes.
I can answer your first query why its dyanamic name this is because themes which you installed are ghosted version and when you apply them an unghosted version is created for the specific site where it is applied. so a dyanamic naming is required and it cannot be hard coded in MOSS even if you try using SPD you can do it but you have to remove the theming then.
the same you have also have notified in update that the css name is changed only when you apply it.
regarding your second issue of reapplying it did you try applying another them and then back to first one and is giving error then please check the 12 hive logs it will give you cause of failure and if still you are not able to figure out the same plz share the relavent log here we will try to help you
I have a custom feature which adds a few controls into the AdditionalPageHead DelegateControl. This works fine on any sites which use our default.master. However the project requires the use of a publishing site which has a master page derived from BlackBand.master (which does not have the AdditionalPageHead DelegateControl included), so I made a copy of the master page from the master page gallery on the appropriate site collection and then modified it to include the following line:
<SharePoint:DelegateControl
ID="DelegateControl1"
runat="server"
ControlId="AdditionalPageHead"
AllowMultipleControls="true"/>
This should therefore include this DelegateControl within all pages using this master page. However when this is uploaded as a new version of BlackBand.master and approved as such, all the pages in the site that use it get a 404 error as if they no longer exist. If I restore the previous version of the master page then everything return to normal.
Help is appreciated as always.
The answer was that I was approaching the solution to my problem incorrectly.
To fix this I opened SharePoint designer at my site collection root and clicked on _catalogs/masterpage. Then I made a copy of BlackBand.master in the masterpage catalog. Opened it and added my line of code. Saved it and then set it as my default and custom master page (to ensure that it applied to any straight up web part pages as well as layout pages).
This worked without a problem.
I have a site with multiple document libraries in it. One of the site users has full control of the site & at one point, instead of creating a new document library, they renamed the default document library from "Shared Documents" to "Correspondence". Now they've opened the document library in windows explorer, so it's added an entry into their network places. The name of the entry was "Shared Documents on portal.mydomain.net" and not "Correspondence on portal.mydomain.net". This is because the address of the library is still "Shared Documents". I went into the user's network places and renamed the entry, however I would prefer to have the address changed as well, so that future users do not run into the same problem.
I looked in the Document Library Settings but couldn't find a place to change the address there. The address gets displayed in "Title, description and navigation" but there is no option to change it. I tried looking under Site Actions > Site Settings > Content and structure to see if there was any way to change the address there. However, when I check off the Correspondence document library and pull down the actions menu, "Move" is greyed out.
I suppose that I could save the library as a template, include the content & make a new library in the proper address, but then the modified by information would all be wrong.
Any ideas?
Renaming the document library in SharePoint Designer changes the address.
Open the library in Windows Explorer, and just rename the folder. Works in Sharepoint Foundation 2010.