by Gustaf Westerlund | Sep 20, 2006
Well, sometimes it’s better to look first and blog second,
I looked around a bit and found that the CRM Team Blog actually have an entry on how this works. Have a look here: https://blogs.msdn.com/crm/archive/2006/08/15/701230.aspx
The SubscriptionSyncInfo table seems to be the place where all syncs are logged to the database. Very usefull for checking if a users sync has been successfull and how often it has been done.
Gustaf Westerlund
CRM and SharePoint Consultant
Humandata AB
www.humandata.se
by Gustaf Westerlund | Sep 20, 2006
There are a couple of tables in the database that handle the Outlook-CRM Syncronization and the offline sync. I havn’t been able to find any further documentation on exactly how it works, but will publish any more info I find on the subject on this blog. There are mainly three normal tables concerned, namely:
Subscription
SubscriptionClients
SubscriptionSyncInfo
There are also several tables created for each user that contains their specific sync data. These are named:
SyncEntry_987F788E642CDB1184900007E94DD8DB
I would like to point out that these tables both contain info on Outlook-CRM sync and CRM Offline sync (ie Main SQL – MSDE sync).
If anyone has any more info on the subject, please contact me, I would like to discuss the matter.
If I find the time, I would like to research this a bit more. If I do, I’ll let you know…
Gustaf Westerlund
CRM and SharePoint Consultant
Humandata AB
www.humandata.se
by Gustaf Westerlund | Sep 11, 2006
JavaScripting and quick create forms
For you who haven’t already noticed, if you create an OnLoad JavaScript for Account, Contact or any other entity and it includes some sort of defaulting of field values, if this field is not compulsory, it is not included in the quick create form, hence the onLoad event will send an error when the form is loaded. So, just check that it is there first 🙂
Gustaf Westerlund
CRM and SharePoint Consultant
Humandata AB
www.humandata.se
by Gustaf Westerlund | Aug 30, 2006
Developing Callouts
When developing callouts, many of you have probably gone mad by all the waiting due to the fact that the IIS has to be stoped and started between every compilation, and then most of the CRM application has to be recompiled again when you try to access the page. I have tried to find a good solution on how to bypass this, some including trying to shut down the AppPool instead of the IIS, but I couldn’t get it to work.
This evening, I read a blog about how you can do it! This great guy has developed a small program that just calls your callout like the CRM normally does, only you can do it in your local computer instead! Great for debugging! A simple a ingeniuos solution, why didn’t I think of that?
You can find it at: http://www.stunnware.com/crm2/topic.aspx?id=LocalCalloutDebugging
Gustaf Westerlund
CRM and SharePoint Consultant
Humandata AB
www.humandata.se
by Gustaf Westerlund | Aug 30, 2006
On taking backup
When taking backup of your CRM system, to avoid any later problems consider the following:
– Take a complete backup of the xxxx_MSCRM database.
– Take a complete backup of the xxxx_METABASE.
– And just to be sure, export all customizations to an xml-file.
– Make a backup of the Microsoft CRMServerbinassembly (normally found in Program Files)
– Make a backup of all custom aspx and html pages and code from the external website.
If you have any customizations what so ever, make sure you take a backup of the METABASE att same time as the MSCRM-database. If you do not, you might encounter inconsistencies at a later date which might be hard to fix. I’m planning on writing about what you do if this happens anyway.
If you have made any changes to the reports you should also backup the main SQL Reporting Services database, but hopefully have the rdl:s somewhere else aswell.
Gustaf Westerlund
CRM and SharePoint Consultant
Humandata AB
www.humandata.se
Recent Comments