Hi
Anyone else experienced with upgrade of the marketing app to latest version, when you create a new segment the designer asks you to choose which type of segment you want to create. Then selected static and now when I create a new segment there is no option to choose which type of segment and it defaults to static and is read only.
Brad
Hi Clofy
The only query definition available is the filter on contact no option to select the new types of segments in wave 2 release
Brad
HI Brad,
You could log a call with MS because segment query works well in most of time,
but I suggest you could still try troubleshoot by yourself before contact for support.
Regards,
Clofly
Thanks Clofy yes we are on the wave 2 release. Do you not think its better i log a call with MS as its sounds more like an issue with the upgrade that caused this?
Hi Brad,
It's(Query definition) also not available in form editor ?
Regards,
Clofly
Thanks for your reply but the segment selection is no longer available and therefore it defaults to static and its read only
Hi Brad,
From your description, is your current version wave 2 release ?
1. You could create a simple dynamic segment with script by web api below to test whether your current user has sufficient privileges to create segment entity firstly.
var data = { "msdyncrm_segmentname": "Test Segment", "msdyncrm_segmentquery": "PROFILE(contact, contact_1) .FILTER(contact_1.lastname CONTAINS 'XXX')", "msdyncrm_segmenttype": 192350000, "statuscode": 192350006 } var entity = "msdyncrm_segment"; var req = new XMLHttpRequest(); req.open("POST", Xrm.Page.context.getClientUrl() "/api/data/v9.0/" entity "s", true); req.setRequestHeader("OData-MaxVersion", "4.0"); req.setRequestHeader("OData-Version", "4.0"); req.setRequestHeader("Accept", "application/json"); req.setRequestHeader("Content-Type", "application/json;charset=UTF-8"); req.setRequestHeader("Prefer", 'odata.include-annotations="*"'); req.onreadystatechange = function() { if (this.readyState === 4) { req.onreadystatechange = null; if (this.status === 204) { Xrm.Utility.alertDialog('ok'); } else { Xrm.Utility.alertDialog(req.statusText); } } } req.send(JSON.stringify(data));
2. Make a backup unmanaged solution, add segment entity and select information main form in it.
Remove Query definition field and publish (1) it to test whether the field has been removed on form.
Drag the field back to section again, and double click to edit its Controls properties,
set CC_SegmentationIFrameFilterQuery field to msdyncrm_segmentfilterquery (Multiple),
set CC_SegmentationIFrameMemberIds field to msdyncrm_segmentmemberids (Multiple);
then publish the form again to test whether designer could come back.
Regards,
Clofly
Hi @Brad Henning,
This is working as expected. You can see a comparison between the way segments worked before and after the upgrade at the link below.
Long story short, the purpose of your segment (demographic , ..combined audience, behavioural , etc..) now pre-defines the segment type for you (making your life easier, hence the disabled field).
Demographic and firmographic =>Both options pre-populate the segment type as dynamic.
Combined audience => pre-populates with compound
André Arnaud de Cal...
292,074
Super User 2025 Season 1
Martin Dráb
230,900
Most Valuable Professional
nmaenpaa
101,156