I got a chance to sit with Microsoft Folks abt BDC and Infopath Issues. Let me keep posted once i got an full update from Microsoft.
P.S: Due to site restrictions, i'm attaching excel sheet to get clear view.
| Issue | Scenario | Microsoft Recommendation |
| BDC Filtering | Multiple Filtering is unavailable on the BDC SharePoint List Web Part. On a regular SharePoint List filtering is available. | Not possible/available or cannot be done |
| Filter Pattern Re-arrangement | Search parameters are fixed to “is equal to”, “starts with”, “ends with” and “contains”. We would like to change the order in which these appear in the menu and/or remove some parameters. In our interface “is equal to” would hardly be used; however, it is the first option available. In fact, we may want to only use “contains”. | Not possible/available or cannot be done |
| Lack of handling Co-related sub queries | The BDC does not handle joining of tables together unless a joined view is provided by the database. That is not what is desired. Basically, without this capability within the BDC layer, a parent child relationship requires this relationship to be displayed in two web parts (i.e. one parent web part and one child web part). We would like to have a single joined view displayed in the user interface and have that join performed in the BDC layer. | Not possible/available or cannot be done |
| Parent Child Relationship | If a parent / child relationship is used using two web parts, the search on the parent does not update the results of the child web part. Thus, if the results of the search change the display of the parent, then what is shown in the child web part is inaccurate. Only when you select an item from the parent web part, the child web part is updated. This causes confusion to the end user. | It's a bug in BDC Architecture |
| More than 4 or more criteria Exception | Server Error in '/' Application. ——————————————————————————– Input string was not in a correct format. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.FormatException: Input string was not in a correct format. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace:[FormatException: Input string was not in a correct format.] Microsoft.SharePoint.Portal.WebControls.BusinessDataListWebPart.filterFindButton_Click(Object objSender, EventArgs ea) +894 Microsoft.SharePoint.Portal.WebControls.PostbackLink.OnClick() +59 Microsoft.SharePoint.Portal.WebControls.PostbackLink.RaisePostBackEvent(String eventArgument) +54 Microsoft.SharePoint.Portal.WebControls.PostbackLink.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +31 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +174 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5102 |
It's a bug in BDC Architecture |
| BDC not handling sharepoint groups | In the ACL permission list found in the Application Definition File (Meta Data) for BDC LOB, it only displays NT Groups and not our SharePoint Groups, this limits our control of user access. Other parts of SharePoint do allow using SharePoint Security Groups. | Not supported/ Cannot be done |
| Attachments not suppoted | The BDC does not support attaching images (for example) so that these images can be displayed as part of the BDC SharePoint List table view. SharePoint list do allow embedded images, but the BDC does not support it. | Not possible/available or cannot be done |
| Tooltip produces headache in Infopath browser-enabled forms | Tool tips cover the field names when displayed in InfoPath 2007 Browser-Enabled Webpage. There appears to be no way to control the display of tool tips. | Not possible in Infopath but you can done by custom javascript |
| Attachments cannot be published in Infopath | If the InfoPath form has an attachment, the attachment is embedded within the form XML. We would like to be able to place this attachment as a separate field in the forms library, but it does not appear possible. Error Message: The selected field cannot be promoted because its data type is not supported: base64Binary | Not possible and cannot be done |
| Not able to connect between sharepoint list(instead of Forms Library) and Infopath | It does not appear possible to link an InfoPath form to a SharePoint list. Instead of having the default forms view used with SharePoint, we would like to use InfoPath forms. Thus, the NEW option from a SharePoint list does not give us the flexibility required by our users. Our users like to see more formal forms and InfoPath could provide that, but we can't seem to interface a SharePoint List with an InfoPath form. | Not possible and cannot be done |
| BDC Scability/Performance Issues | In general, we find slow/low performance when using the BDC. What are potential areas that performance may be degraded by using the BDC? | |
| Custom Action with Long URL | I would like to add an custom action which should redirect to Infopath Browser URL with Parameter from BDC. I've added a custom action and URL(Longest URL) – If i view this custom action in Business Data Catalog, it truncating my URL. I hope it has some limited size for URL field. I would appreciate if you any one can suggest me a way to achive this task?
Shorter version: I need to pass a parameter from BDC to Infopath(obvisouly Infopath Form Services Browser URL would be a Longest URL Path). If i assign this Longest path to custom action, It's not accepting…. |
It's a bug in BDC Architecture |
lovedjohnysmith