Hi all, As you all know, scheduled publishing will not run automatically unless you enable PublishAgent task in Sitecore config. By default, all items that are in publish queue will get published when this task triggers. This includes all items in the final workflow state and all items that don't have workflows. Sometimes this is not what you want. Maybe you don't enable workflow on media items and you don't want the items to go live when they are not ready. The workaround is to create your own PublishAgent task. Looking at the one provided, we can easily extend the code to insert the RootItem to the PublishOptions (this only works with Full or Smart publish mode however): You will notice that on the Run method I check whether the server time is around the time I set in the parameter (thanks to this post for the code). This will enable us to run the task near the specific time we set (e.g. midnight). In the config patch, just add this to enable the custom agent...
Hi all, Trying to use AjaxControlToolkit with SharePoint 2013, I managed to make this work using the following steps: 1. Download latest (.NET 4.5) version from http://ajaxcontroltoolkit.codeplex.com/releases/view/112805 2. Add Reference in your VS solution (both AjaxControlToolkit and AjaxMin dlls) 3. In Package designer, create safe control entries for both: 4. SP Web.config needs to have the AjaxControlToolkit assembly in compilation/assemblies node. I use SPWebConfigModification in feature receiver (web application scope) to do this. 5. Replace the default ScriptManager in your masterpage with the ToolkitScriptManager 6. Important: Move this section from the head tag to the body tag in your master page after the ToolkitScriptManager to avoid databind issue That's all I had to do. I used the Ajax Combobox and bind my datasource in code behind and it is working fine. HTH, Andreas
I encountered this error in my project when trying to run CRM reports within CRM (including the default reports). In the reportservice logs it says: Cannot create a connection to data source 'CRM'. ---> Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: Immediate caller Domain\SqlService has insufficient privilege to run report as user S-1-5-21-1162093662-620106126-315576832-39399. The CRM is installed on the application server and the SSRS is installed on different server. After futher investigation it turns out that it's caused by double hopping issue regarding the authentication and we just need to set the correct SPN on the machines. setspn -a http/your-crm-server-name domain\crm-user setspn -a http/your-crm-server-name(FQDN) domain\crm-user Other things to check to make sure your reports work: 1. Make sure your SRS connector has the same RollUp version as the CRM Server RollUp 2. In Reporting Service Configuration Manager, unche...
Comments
Post a Comment