I have a custom receive pipeline that makes a stored procedure call to a database. The database connection string and procedure names are “soft coded” as properties on the pipeline. Until now, I’ve set these up on a “per instance” basis, the pipeline used in conjunction with a physical receive location, and it’s always worked great.
Now I want to call the same pipeline from within an orchestration. I found a couple of examples of how to do that. The code works and it all compiles without error. But when the pipeline executes from within the orchestration, the database connection string (property) is null. It’s as if “the property bag” wasn’t loaded before the Execute procedure (of the pipeline was called).
So I’m stumped…..Since you can’t configure a setup for the pipeline without it being attached to a physical receive location (which it’s not, when calling it from an orchestration), how do you define the properties to use? And make sure they load?
Thanks in advance for your thoughts and time.