3

我对 crm 2013 有疑问。我将 fetchXML 用于过滤（例如）计费帐户。当我们的团队使用 CRM 2011 时一切正常，但我们迁移到 CRM 2013 并在添加相关项目时遇到问题。

retrieveRecord( 
                recordId,
                "xxx_project",
                null,
                null,
                function (result) {
                    var xId = (result.xxx_Customer) ? result.xxx_xCustomer : "";

                    // Fetch to retrieve filtered data.
                    var fetch =
                    "<fetch version='1.0' output-format='xml-platform' mapping='logical' distinct='false'>" +
                    " <entity name='xxx_billingaccount'>" +
                    "   <attribute name='xxx_billingaccountid' />" +
                    "   <attribute name='xxx_name' />" +
                    "   <attribute name='statecode' />" +
                    "   <attribute name='xxx_xid' />" +
                    "   <order attribute='xxx_name' descending='false' />" +
                    "   <filter type='and'>" +
                    "       <condition attribute='xxx_xid' operator='eq' value='" + xId + "' />" +
                    "   </filter>" +
                    " </entity>" +
                    "</fetch>";

                    // Columns to display in the custom view (make sure to include these in the fetch query).
                    var layout = "<grid name='resultset' object='1' jump='xxx_name' select='1' icon='0' preview='1'>" +
                    "  <row name='result' id='xxx_billingaccountid'>" +
                    "    <cell name='xxx_name' width='150' />" +
                    "    <cell name='statecode' width='150' />" +
                    "    <cell name='xxx_xid' width='150' />" +
                    "  </row>" +
                    "</grid>";

                    SDK.Entity.BillingAccount.displayFilteredLookupView(gridTypeCode, gridControl, fetch, layout, "Filtered by Customer ID Billing Accounts");
                },
                SDK.Entity.BillingAccount.errorHandler);

displayFilteredLookupView: function (gridTypeCode, gridControl, fetch, layout, viewName) {

        var viewId = "{3D02B064-4D8D-4E7C-B919-965D5D2C225D}";
        var relName = gridControl.GetParameter("relName"),
            roleOrd = gridControl.GetParameter("roleOrd");

        // Creates the custom view object.
        var customView = {
            fetchXml: fetch,
            id: viewId,
            layoutXml: layout,
            name: viewName,
            recordType: gridTypeCode,
            Type: 0
        };

        // Pops the lookup window with our view injected.
        var lookupItems = LookupObjects(null, "multi", gridTypeCode, 0, null, "", null, null, null, null, null, null, viewId, [customView], null, null, null, null, null, null, 1);

        // Once the lookup window is closed, we need the parent record ID and ETC before associating selected records.
        if (lookupItems && lookupItems.items.length > 0) {
            var parent = GetParentObject(),
                parentId = parent.id,
                parentTypeCode = parent.objectTypeCode;

            //associates the selected records 
            AssociateObjects(parentTypeCode, parentId, gridTypeCode, lookupItems, IsNull(roleOrd) || roleOrd == 2, "", relName);
        }

    },

当我搜索解决此问题的路径时，我找到了一个链接http://community.dynamics.com/crm/f/117/p/119416/248998.aspx。这对我们的项目来说非常糟糕。

也许任何人都可以帮助我解决这个问题......

4

2 回答 2

4

您应该将LookupObjects功能更改为LookupObjectsWithCallback功能：

LookupObjectsWithCallback(callbackReference, null, "multi", gridTypeCode, 0, null, "", null, null, null, null, null, null, viewId, [customView], null, null, null, null, null, null, 1);

并在这样的代码中调用它：

   displayFilteredLookupView: function (gridTypeCode, gridControl, fetch, layout, viewName) {

        var viewId = "{3D02B064-4D8D-4E7C-B919-965D5D2C225D}";
        var relName = gridControl.GetParameter("relName"),
            roleOrd = gridControl.GetParameter("roleOrd");

        // Creates the custom view object.
        var customView = {
            fetchXml: fetch,
            id: viewId,
            layoutXml: layout,
            name: viewName,
            recordType: gridTypeCode,
            Type: 0
        };
        // Get all necessary parameters, that you want to pass into your callbackReference function.
        SDK.Entity.BillingAccount.callbackReference.gridTypeCode = gridTypeCode;
        SDK.Entity.BillingAccount.callbackReference.relName = relName;
        SDK.Entity.BillingAccount.callbackReference.roleOrd = roleOrd;

        // Pops the lookup window with our view injected.
        LookupObjectsWithCallback(SDK.Entity.BillingAccount.callbackReference, null, "multi", gridTypeCode, 0, null, "", null, null, null, null, null, null, viewId, [customView], null, null, null, null, null, null, 1);                
    }

你SDK.Entity.BillingAccount.callbackReference是一个具有属性的对象callback, gridTypeCode, roleOrd, relName:

 callbackReference: {

    callback: function (lookupItems) {

        // Once the lookup window is closed, we need the parent record ID and ETC before associating selected records.        
        if (lookupItems && lookupItems.items.length > 0) {
            var parent = GetParentObject(),
                parentId = parent.id,
                parentTypeCode = parent.objectTypeCode;

            //associates the selected records 
            AssociateObjects(parentTypeCode, parentId, SDK.Entity.BillingAccount.callbackReference.gridTypeCode, lookupItems, IsNull(SDK.Entity.BillingAccount.callbackReference.roleOrd) || SDK.Entity.BillingAccount.callbackReference.roleOrd == 2, "", SDK.Entity.BillingAccount.callbackReference.relName);
        }
    },
    gridTypeCode: null,
    roleOrd: null,
    relName: null
}
于 2014-03-12T18:06:29.837 回答
0

我无法使上述建议起作用。我认为这是我对如何定义对象'callbackReference'缺乏了解。当我按照上面记录的方式粘贴代码时，Visual Studio 会抱怨。下面是代码，没有用。

var locAssocObjAction1 = {

    callback: function (lookupItems) {

        //debugger;
        // Once the lookup window is closed, we need the parent record ID and ETC before associating selected records.        
        if (lookupItems && lookupItems.items.length > 0) {

            var parent = GetParentObject(),
                parentId = parent.id,
                parentTypeCode = parent.objectTypeCode;

            //associates the selected records 
            AssociateObjects(parentTypeCode, parentId, params.gridTypeCode, lookupItems, IsNull(roleOrd) || roleOrd == 2, "", relName);

        }
        Xrm.Utility.alertDialog("Message on alert dialog", function () { });
    }
}

//pops the lookup window with our view injected
LookupObjectsWithCallback(locAssocObjAction1, null, "multi", params.gridTypeCode, 0, null, "", null, null, null, null, null, null, viewId, [customView]);

作为一种解决方法，我找到了以下解决方案：

http://www.magnetismsolutions.co.nz/blog/paulnieuwelaar/2014/04/21/filter-nn-add-existing-lookup-dynamics-crm-2013

上述建议与 Paul Nieelaar 的主要区别如下

var callbackRef = Mscrm.Utilities.createCallbackFunctionObject("locAssocObjAction", this, parameters, false);

//pops the lookup window with our view injected
LookupObjectsWithCallback(callbackRef, null, "multi", gridTypeCode, 0, null, "", null, null, null, null, null, null, viewId, [customView]);

}

我不确定“locAssocObjAction”的实现是什么。但是，N:N 关联似乎有效。

干杯!

于 2014-05-14T20:22:25.790 回答