How to add ToLogicalID to COR_OUTBOD_HEADER table

Hi,

I'm working on IDM Workflow where a Sync.ContentDocument BOD will be publish when file is uploaded.

I'm getting error "Message cannot be routed" and notice that both Sync.ContentDocument and Process.ContentDocument BODs does not contain "ToLogicalId" header.

According to Vignesh answer, the ToLogicalID must be present in the OUTBOD_HEADER table.

I would like to know how to add a row/ set ToLogicalID to COR_OUTBOD_HEADER table in DB?

	Error message description
	Screen capture of ProcessContentDocument BOD
	Table row of COR_OUTBOD_HEADER

Thanks in advance

Best Regards,
YS

Find more posts tagged with

ION Connect

Accepted answers

Legacy Contributor

Solved the issue by updating the connection point Name to 1 and Type to daf (logicalID = infor.1.daf).

On the previous setting, the Sync message was send from infor.1.daf but my connection point logicalID is infor.IDM.idm. Since the Process message logicalID is determine from Sync message. Thus, ION unable to route the Process message to the connection point.

Reference: IDM Configuration Guide for Infor ION

All comments

Kevin Heiman

The To Logical ID is required for the Process pattern. Sync typically would not have a To Logical id.

Using a To Logical Id causes ION to not apply routing rules, but rather indicates that the message is to be sent directly to the To Logical ID regardless of any Data Flow defined.

In case it is needed, adding notation that you can explicitly override routing. https://docs.infor.com/ion/2020-x/en-us/iondeskceug/default.html?helpcontent=ibc1566812260423.html

But I don't think that is where you are wanting to go.

The Process workflow result is normally routed to the lid://infor.daf.daf logical ID. As noted, the Process To Logical Id is determined from the From Logical Id of the Sync that started the workflow.

If the From Logical ID on the Sync is missing, then that needs to be corrceted. Can we assume this is on premise and possibly there is something in the configuration that may not be correct?

Legacy Contributor

Hi Kevin Heiman,

Yes it is on premise, I am new to BOD and might misconfigure something. You are correct the Sync is missing the FromLogicalID header.

	Screen capture of Sync.ContentDocument BOD
	Information from OneView

Do let me know if you need any further information, thank you!

Best Regards,
YS

Legacy Contributor

Solved the issue by updating the connection point Name to 1 and Type to daf (logicalID = infor.1.daf).

Reference: IDM Configuration Guide for Infor ION

Copyright © 2025 Infor. All rights reserved.