![]() |
|
|
#1 |
|
Guest
Posts: n/a
|
Workflow GUID
All,
We have created a workflow that uses an step - send e-mail. Since we could not just e-mail to a static e-mail address, we created a contact and assigned the e-mail to this contact. In our workflow, we call this contact in the e-mail send to. All this works fine. The client has a development, QA, staging and production environments. When we move the workflow from one environment to another, the workflow stops working. The reason being the GUID for contact having the e-mail changes from one environment to another. Is there a way to manage this? Can we make sure for some specific record, the GUID remains the same across different environments? Thanks, Shikhar |
|
|
|
#2 |
|
Guest
Posts: n/a
|
Re: Workflow GUID
Shikhar;
I have one supported option: If you were to redeploy the client's production database to both DEV and QA, then the contact will have the same contactid in all 3 environments. as long as the contact is never deleted or merged, the contactid should always be constant. Dave Ireland "Shikhar" <> wrote in message news:... > All, > > We have created a workflow that uses an step - send e-mail. Since we could > not just e-mail to a static e-mail address, we created a contact and > assigned > the e-mail to this contact. In our workflow, we call this contact in the > e-mail send to. > > All this works fine. The client has a development, QA, staging and > production environments. When we move the workflow from one environment to > another, the workflow stops working. The reason being the GUID for contact > having the e-mail changes from one environment to another. > > Is there a way to manage this? Can we make sure for some specific record, > the GUID remains the same across different environments? > > Thanks, > > Shikhar > |
|
|
|
#3 |
|
Guest
Posts: n/a
|
Re: Workflow GUID
Write some code to crreate your "contact" with a common Guid in all
environments- yes - you can set the Guid of a new record in and entity using the SDK Pete "Dave Ireland" <> wrote in message news:.gbl... > Shikhar; > > I have one supported option: If you were to redeploy the client's > production database to both DEV and QA, then the contact will have the > same contactid in all 3 environments. as long as the contact is never > deleted or merged, the contactid should always be constant. > > Dave Ireland > > > "Shikhar" <> wrote in message > news:... >> All, >> >> We have created a workflow that uses an step - send e-mail. Since we >> could >> not just e-mail to a static e-mail address, we created a contact and >> assigned >> the e-mail to this contact. In our workflow, we call this contact in the >> e-mail send to. >> >> All this works fine. The client has a development, QA, staging and >> production environments. When we move the workflow from one environment >> to >> another, the workflow stops working. The reason being the GUID for >> contact >> having the e-mail changes from one environment to another. >> >> Is there a way to manage this? Can we make sure for some specific record, >> the GUID remains the same across different environments? >> >> Thanks, >> >> Shikhar >> > > |
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|
< Windows Help - MS Office Help - Hardware Support >
| New To Site? | Need Help? |