Hi all,
I'm aware of some restrictions on doing this and also that Xrm.Page is going to be deprecated, however....
My question is why does it include the {} in the GUID when it returns the string??
Eg When I call this inside my JS
parent.Xrm.Page.data.entity.getId();
The value is a GUID but formatted as {GUID}
*This post is locked for comments
Hi,
I am also agreed with you. But seems this due to maintain the structure and JSON serialization.
You may noticed while we are passing GUID inside FetchXML we have to provide GUID inside {} . In other hand while we are passing GUID inside WEB API query we are passing without {} .
So there is no consistency but we have to maintain the way MS provided.
Hi,
parent.Xrm.Page.data.entity.getId();
The id parameter passed to the URL is the encoded id value for the record. In this example the id value is {899D4FCF-F4D3-E011-9D26-00155DBA3819}. The encoded version of the GUID substitutes opening and closing brackets “{” and “}” with “%7B” and “%7D”, respectively,
We need to replace braces
var fcProfileId = Xrm.Page.data.entity.getId();
fcProfileId = fcProfileId.replace('{', '').replace('}', '');
Thanks
Ridhima
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,235
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (