DBXL Sharepoint Mapping: When Object Model should work but doesn’t - Ernesto Machado
in

InfoPath Dev

Ernesto Machado

DBXL Sharepoint Mapping: When Object Model should work but doesn’t

When creating a Sharepoint mapping from the DBXL Administration Tool (DAT) you have two options: Object Model and Web Service. Web Service is required when the Sharepoint instance lies on a different server. However, we have seen instances where Object Model produces an error, even though DBXL and Sharepoint are on the same machine.

How do you know if you’re in this situation?

  1. Add a Sharepoint mapping. Select Web service. Save the document type. Add documents and verify that everything works as expected.
  2. Edit the same doctype to use Object Model. When you click Save in DAT you get this:

 

Simply using Web Service is an acceptable workaround for some people. But if you wish to use IPFS (browser enabled forms) you’ll need to use Object Model. So how do we fix this?

When faced with this scenario please check the Applications eventlog. It is our experience that we find a SharePoint error with Network Service not having permission to access the Sharepoint database.  Evidently, the object model does direct database access. To fix this, switch DBXL to use the same identity as the SharePoint app pool.

Published Jan 22 2010, 07:55 PM by ErnestoM
Filed under:

Comments

 

Twitter Trackbacks for DBXL Sharepoint Mapping: When Object Model should work but doesn???t - Ernesto Machado [infopathdev.com] on Topsy.com said:

Pingback from  Twitter Trackbacks for                 DBXL Sharepoint Mapping: When Object Model should work but doesn???t - Ernesto Machado         [infopathdev.com]        on Topsy.com

January 27, 2010 8:13 PM
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.