使用关联集提升InterchangeID不起作用-为什么不呢? [英] Promoting the InterchangeID using a correlation set doesn't work - why not?

查看:62
本文介绍了使用关联集提升InterchangeID不起作用-为什么不呢?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个直接发送到MessageBox的发送端口,用于发布一条消息,为此,我希望将其InterchangeID升级,以便可以针对当前的这批消息创建顺序的车队.我正在使用一个初始化相关集,将BTS.InterchangeID声明为相关属性,并将其应用于Send操作.

I have a Direct to MessageBox send port publishing a message, for which I would like to have the InterchangeID promoted so that I can create a sequential convoy against the current batch of messages. I am using an initializing correlation set, declaring BTS.InterchangeID as the correlated property, and applying it to the Send action.

当我运行代码时,这些消息会导致路由错误.查看路由失败报告,我可以看到存在InterchangeID,但它是未提升"的.

When I run the code, these messages cause routing errors. Looking at the routing failure report, I can see that the InterchangeID is present but is "Not Promoted".

为什么在这种特殊情况下,关联集通常不能正常工作,却不能提升属性?

Why in this particular case is the correlation set not promoting the property when this usually just works?

推荐答案

我建议您创建自己的仅消息上下文属性,可以使用 BTS.InterchangeID 值进行设置,而不是尝试进行更改现有BizTalk的属性,因为它可能会带来意想不到的后果.

I would suggest you create your own message only context property that you can set using the BTS.InterchangeID value rather than trying to change the properties of an existing BizTalk one as it might have unintended consequences.

这篇关于使用关联集提升InterchangeID不起作用-为什么不呢?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆