如何解决Apache Camel Salesforce组件:是否支持“次要”关系?
我正在从Jitterbit迁移到Camel,以满足我们的数据集成需求。
但是我面临着骆驼Salesforce组件的严重问题。有问题的SOQL查询是:
SELECT Account.Owner.Id,Lookup(User)
Account.Owner.Name,Lookup(User)
Id,Name,Owner.Id,Lookup(User)
Owner.Name,Lookup(User)
QualifyingRep__r.Name,Lookup(User)
Solution_Architect__r.Name,Lookup(User)
StageName,Type,(SELECT
Id,Product2.Name,Lookup(Product)
Quantity,TotalPrice,UnitPrice
FROM OpportunityLineItems
),CurrencyIsoCode,SplitAmount,SplitOwner.Id,Lookup(User)
SplitOwner.Name,Lookup(User)
SplitPercentage,SplitType.MasterLabel Lookup()
FROM OpportunitySplits
)
FROM Opportunity
WHERE StageName = 'Closed Won'
我添加了Lookup(User)
来注释存在的“未成年人”关系。
返回的JSON是:
{
"attributes": {
"referenceId": null,"type": "Opportunity","url": "/services/data/v49.0/sobjects/Opportunity/<guid>"
},"Type": "New Revenue","StageName": "Closed Won","Account": {
"attributes": {
"referenceId": null,"type": "Account","url": "/services/data/v49.0/sobjects/Account/<guid>"
}
},"OpportunityLineItems": {
"done": true,"totalSize": 5,"nextRecordsUrl": null,"records": [
{
"attributes": {
"referenceId": null,"type": "OpportunityLineItem","url": "/services/data/v49.0/sobjects/OpportunityLineItem/<guid>"
},"Quantity": 1.0,"UnitPrice": 11990.0,"TotalPrice": 11990.0,"Name": "XXXXXXXXXXXXXXXXXXXXXX YYYYYYYYYYYYY","Id": "<guid>"
},{
"attributes": {
"referenceId": null,"CurrencyIsoCode": "USD","UnitPrice": 2758.0,"TotalPrice": 2758.0,"Name": "XXXXXXXXXXXXXXXXXXXXXX ZZZZZZZZZZZZZZ","Id": "<guid>"
}
]
},"OpportunitySplits": {
"done": true,"totalSize": 2,"type": "OpportunitySplit","url": "/services/data/v49.0/sobjects/OpportunitySplit/<guid>"
},"SplitPercentage": 100.0,"SplitAmount": 23392.0,"SplitPercentage": 0.0,"SplitAmount": 0.0,"Name": "XXXXXXXXXXXXXXXXXXXXXX","Id": "<guid>"
}
注意::查询结果应与名称分开,但不返回任何一个。这是一个止步不前的方法,因为集成的目的是在另一个系统中计算佣金(我们绝对必须知道要向谁付款)。
在生成DTO时,camel-salesforce-maven-plugin
也会发生同样的事情-那里也不支持这些关系。实际上,在将Salesforce DTO的转换迁移到目标DTO时,我首先注意到了这个问题。它返回Opportunity.Account.OwnerId
,而不是User
返回String
对象。
之所以提出这个问题,是因为Opportunity
DTO既有Account
又有AccountId
返回了一个Account
对象和一个String
。如果所有生成的DTO都遵循此模式,就不会有问题。
我相信Jitterbit使用Salesforce SOAP API-所有这些都是在幕后进行的,因此我不确定。 肯定是一件事,Salesforce中定义的所有关系都可以在Jitterbit中找到,所以我对Camel Salesforce组件中发生的事情感到困惑。
我是否需要做一些事情以使DTO中生成 all 关系,并且当然要让查询返回请求的 ?
更新
我已经在POSTMAN中使用简化查询对此进行了测试:
{{instance_url}}/services/data/{{api_version}}/query?q=SELECT Id,Account.Owner.Name FROM Opportunity WHERE StageName = 'Closed Won' AND id = '<guid>'
返回的JSON是:
{
"totalSize": 1,"done": true,"records": [
{
"attributes": {
"type": "Opportunity","url": "/services/data/v49.0/sobjects/Opportunity/<guid>"
},"Id": "<guid>","Name": "XXXXXXXXXXXXXXXXXXXXXXX","Account": {
"attributes": {
"type": "Account","url": "/services/data/v49.0/sobjects/Account/<guid>"
},"Owner": {
"attributes": {
"type": "User","url": "/services/data/v49.0/sobjects/User/<guid>"
},"Name": "<user name>"
}
}
}
]
}
虽然经过大量修改,但Account.Owner.Name
路径很明显,这向我暗示这是Camel Salesforce组件问题。
解决方法
在这种情况下,解决方案是确保正确生成所有DTO。
首先,请确保插件列出了正确的对象名称:
<includes>
<include>Account</include>
<include>Invoice__c</include>
<include>Opportunity</include>
<include>OpportunityLineItem</include>
<include>OpportunitySplit</include>
<include>OpportunitySplitType</include>
<include>Product2</include>
<include>User</include>
</includes>
就我而言,我是第一次使用Invoice
和Product
。
然后我逐行比较查询,并确保生成的DTO支持所有关系。 这需要在缺少关系的地方进行手动操作。
例如,有必要在“机会”中添加发票:
@XStreamAlias("Invoice_2014__r")
private Invoice__c Invoice_2014__r;
/**
* @return the Invoice_2014__r
*/
@JsonProperty("Invoice_2014__r")
public Invoice__c getInvoice_2014__r() {
return Invoice_2014__r;
}
/**
* @param Invoice_2014__r the Invoice_2014__r to set
*/
@JsonProperty("Invoice_2014__r")
public void setInvoice_2014__r(Invoice__c Invoice_2014__r) {
this.Invoice_2014__r = Invoice_2014__r;
}
当DTO完全支持该查询时,一切都会按预期进行。
我不明白DTO为什么需要手动干预,因为所有必需的关系都已通过工作台(https://workbench.developerforce.com)进行了定义和观察。
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。