I have also encountered the above scenario on 7.3 sp3, however exact code works perfect on 7.2d, Is there a solution for this?

My suspicion is that something will have changed in the eWare.dll. This in turn may have changed the way the COM API worked and because of COM interop has had an unintended impact on the .NET API.

Are you using the web class or the specialised classes?

And have you logged this as a case?

Hi Jeff,

Thanks for responding, I'm using the specialized class, DataPageEdit.

Regards,

Tanyaradzwa

I have the above issues when upgrade from 7.1 to 2017 r3; Is there a solution for this?

I have the same problem on

Sage CRM 2017 R3

Before I set the context, i rewrite the URL and redirect to custom entity context.

// BUG SetContext

var iDomKey = Keys[(int)Sage.KeyList.DominantKey];

if (iDomKey != (int) Sage.KeyList.CustomEntity)

{

var url = UrlDotNet(ThisDotNetDll, ThisDotNetFunction);

var newUrl = url.Replace($"&Key0={iDomKey}", $"&Key0={(int)Sage.KeyList.CustomEntity}") + "&T=CustomEntityTabName";

Dispatch.Redirect(newUrl);

}

SetContext("CustomEntityName", int.Parse(customEntityId));

Sven

I only have Sage CRM 2018 R1 on my machine.

I can use the following to set the context of the record and add it into the Recent list.

public ProjectDataPage()

: base("Project", "proj_projectid", "ProjectNewEntry")

{

this.SetContext("Project", Id, true);

}

Won't your code redirect before it ever executes the

SetContext("CustomEntityName", int.Parse(customEntityId));?

Hi Jeff - regarding your above post where you suggest:

public ProjectDataPage()

: base("Project", "proj_projectid", "ProjectNewEntry")

{

this.SetContext("Project", Id, true);

I have a web class page and I've tried both of these, and neither has worked:

this.SetContext("Project", intRecordID, true);

SetContext("Project", intRecordID);

Is there anything different we need to do for a web class page?