我对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。这对我们的项目来说非常糟糕。
也许有人可以帮我解决这个问题...
答案 0 :(得分: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
}
答案 1 :(得分:0)
我无法使上述建议起作用。我认为我对如何定义对象&callbackReference&#39;缺乏了解。当我按上面记录的方式粘贴代码时,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]);
作为一种解决方法,我找到了以下解决方案:
上述建议与Paul Niewelaar的主要区别在于以下
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]);
}
我不确定实施是什么&#39; locAssocObjAction&#39;。但是,N:N协会似乎有效。
干杯!