Objectregardingid Set from Custom URL

(0) Share

Report

Posted on by lauren@lauren.mn

Hi,

I am working on trying to set a campaign response's objectregardingid from a custom URL built by a vbscript. It worked fine in 2011 but in 2015, it is not working. The GUID is correct and so are the parameters. When regardingobjectid and regardobjectname are removed, the campaign response populates all the parameters correctly. I tried removing each parameter one at a time and vice versa, neither worked.

https://contoso.com/main.aspx?etc=4401&pagetype=entityrecord&extraqs=po_contact%3D2997578C-E7B7-E411-98F7-005056BA0CF2%26po_contactname%3DJohn%26telephone%3d(612) 555-5555%26po_state%3d936710023%26po_zipcode%3d55433%26emailaddress%3djohn@test.com%26regardingobjectid%3d6C397BE1-CFA4-E511-B8EB-005056BA0CF6%26regardingobjectidname%3dTEST CAMPAIGN%26po_campaignactivityid%3d742F540C-D0A4-E511-B8EB-005056BA0CF6%26po_campaignactivityidname%3dTest Campaign Activity Name

Thoughts?

Lauren

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (1)

Suggested answer

Community Member on at

Like (0)

Report

Hi Lauren,

Looks like you're missing regardingobjectidtype and po_campaignactivityidtype in your query string. Can you try adding those and see if that works? Here is a link for reference:

https://msdn.microsoft.com/en-us/library/gg334375.aspx#BKMK_setValueLookupfields

Was this reply helpful? Yes No
lauren@lauren.mn on at

Like (0)

Report

Tried adding that in but no luck. But instead of the page just in a handing state, now I get the generic "error try this action again. if the problem continues, check the ms crm community for solution or contact your orgs admin etc etc" so behavior changed but still not quite right

Was this reply helpful? Yes No
lauren@lauren.mn on at

Like (0)

Report

Also as just an observation, I just tried on the Task entity (instead of the campaign response) to add in the regardingobjectid and got the same behavior (ie either stuck hanging or the generic error). However, when I set the parameters just as a normal lookup, the campaign information populates (ie the information that should come in to the regardingobjectid)

This works/populates the custom lookup (set custom lookup but doesn't set regarding)

contoso.com/main.aspx;pagetype=entityrecord&extraqs=po_campaign%3d6C397BE1-CFA4-E511-B8EB-005056BA0CF6%26po_campaignname%3dTEST CAMPAIGN

This does not work (it gives me generic error)

contoso.com/main.aspx;pagetype=entityrecord&extraqs=regardingobjectid%3d6C397BE1-CFA4-E511-B8EB-005056BA0CF6%26regardingobjectidname%3dTEST CAMPAIGN%26regardingobjectidtype%3Dcampaign

This one doesn't work either (this one hangs)

contoso.com/main.aspx;pagetype=entityrecord&extraqs=regardingobjectid%3d6C397BE1-CFA4-E511-B8EB-005056BA0CF6%26regardingobjectidname%3dTEST CAMPAIGN

Thoughts?

Was this reply helpful? Yes No
Verified answer

NatrajY 3,040 on at

Like (1)

Report

You need to specify the entity name (etn) or code (etc) in both the main.aspx query params and in the extraq query params. Try this format

[BASEURL]/main.aspx?etn=[ENTITY NAME]&pagetype=entityrecord&extraqs=?etn%3D[ENTITY NAME]%26regardingobjectid%3D%7B[PARENT RECORD ID]%7D%26regardingobjecttypecode%3D[PARENT ENTITY NAME]%26regardingobjectidname=[DISPLAY NAME OF THE PARENT LOOKUP]

Was this reply helpful? Yes No
lauren@lauren.mn on at

Like (0)

Report

Worked like a charm, thanks!

Was this reply helpful? Yes No