As many of you might notice, upon exporting huge number of records from Smart List (specifically more than 32,767 records) Smart List generates an error, this is actually a bug in GP 2013 which reflect the maximum number the integer can handle. The good thing is that this was resolved in the newly released SP 2: Regards, — Mohammad R. Daoud MVP – MCT MCP, MCBMSP, MCTS, MCBMSS +962 – 79 – 999 65 85 firstname.lastname@example.org http://www.di.jo
I ran into the below error this morning while installing business portal for Dynamics GP 2013: ———————————————————————– Feature Id: 538b415a-89eb-4de6-a93c-9fea1d565363 Location: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions14TEMPLATEFEATURESBPGPReportsCenter Action: Activate Exception: Folder Executive – Company Name does not exist. Stack Trace: at Microsoft.Dynamics.SharePoint.Helper.ValidateFolder(SPList pageLibraryList, String folder) at Microsoft.Dynamics.SharePoint.Helper.AddFolderPermission(String siteRelativePath, String pageLibrary, String folder, String group, String permissionLevel) at Microsoft.Dynamics.GP.BusinessPortal.GPReportsCenter.CenterActivateProcess(String urlCenterLibrary, String quickLunchTitle, String groupName, String groupDesc, String folderName, String pageLibraryName) at Microsoft.Dynamics.GP.BusinessPortal.GPReportsCenter.FeatureActivated(SPFeatureReceiverProperties properties) at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce) at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, Boolean fForce) at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly) at Microsoft.SharePoint.SPFeatureCollection.AddInternalWithName(Guid featureId, String featureName, Version version, SPFeaturePropertyCollection properties, Boolean force, Boolean fMarkOnly, SPFeatureDefinitionScope featdefScope) at Microsoft.SharePoint.SPFeatureCollection.Add(Guid featureId) at Microsoft.Dynamics.GP.Deployment.SharePoint.Office14.FeatureAdapter.Activate(Guid id, FeatureScope scope, String siteCollection, String relativeUrl) at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointActivateFeature.OnPerform(IFeature spFeature, SharePointFeatureInformation spFeatureInfo) at Microsoft.Dynamics.GP.Deployment.WindowsInstaller.SharePoint.SharePointFeatureDeploymentProcessor.Process(IFeature featureInterface, SharePointFeatureCustomActionData data) ———————————————————————– After searching everything on the internet and investigated all possibilities I found finally that one of my companies contains “-“ and “*”, removing these from this company resolved my issue! Regards, — Mohammad R. Daoud MVP – MCT MCP, MCBMSP, MCTS, MCBMSS +962 – 79 – 999 65 85 email@example.com http://www.di.jo
I been in a situation with one of my clients where I been implementing and Active/Active clustering setup over SQL Server 2008 R2 as my customer is still using GP 10.0, after finalizing and testing everything I noticed that the code page I must use is 1256 while I have used 1250!!! Thanks god for having a utilities to update the collation without having to destroy the cluster! I have followed the steps below and it worked like a charm: 1. Backup your objects! As this process will drop logins, linked servers, jobs, and anything related to the instant itself plus will de-attach your database. 2.
It has been finally released, Business Portal 6.0 for Dynamics GP 2013, it still does not support SharePoint 2013 but it has many enhancements could be found HERE . Business Portal 6.0 is supported with the following: Click HERE to go to the System Requirements Page. SharePoint Server 2010 or SharePoint Foundation 2010 only. Windows Server 2008 x64 SP2 or later or Windows Server 2008 R2 SP1 or later. Internet Explorer 8.0, Internet Explorer 9.0, and Internet Explorer 10.0
One of my customers got a case that Journals were not deleting from GL10000 upon posting, this caused the transactions to duplicate between open and work tables and been annoying end users. To fix this miss, I wrote a script that looks into GL10000 and GL10001 and compares the totals between both tables for each journal and generate the result, you can use this script to company these and make sure that all journals were successfully posted and none posted partially.
Guys, If you are planning to upgrade to GP 2013, please consider to analyze your customizations carefully as there might be some changes between the application versions, I been in a situation were we upgraded from GP 2010 R2 to GP 2010 and the customer has a customized report for GL Transaction Entry Inquiry Report, the report didn’t work properly as the core table of the Report has been changed. This is the only thing I found so far, but I wanted to let you know that you might need to plan redoing the customizations of this report upon upgrading to GP 2013. Regards, — Mohammad R.