Change BDC ADF Version Numbers
Posted by ken zheng on May 26, 2008
If you’re hand-coding ADF files and doing a lot of code/import/test cycles, use the version number to make your life easier.
I hate to admit it, but until this week, I was always deleting the ADF and re-importing it. This would break my business data columns and make me re-wire them. All unnecessary.
File this under “it’s obvious once you see it”.
Example:
<LobSystem xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.microsoft.com/office/2006/03/BusinessDataCatalog BDCMetadata.xsd" Type="WebService" Version="1.2.0.0" Name="xyzzyDocumentReview" xmlns="http://schemas.microsoft.com/office/2006/03/BusinessDataCatalog">
Change that version and re-import and the existing business data column uses the updated version automatically with no additional configuration required.
Chad said
I know this post is like a year old but I figured I’d try anyways…
How does the re-import handle modifications? For instance, if you remove a key field or replace it with a different data type? Is there a good place to find out how it handles the numerous modifcation scenarios, or do I just make a change and hope the 2 million items using the BDC don’t break?
Can you revert back to a previous version if it does break something?
ken zheng said
Hi Chad, SharePoint just read whatever from the data source, anything changed in data source just do the full import again.