Posts

Showing posts from April, 2017

opening the solution configuration page using html

<!DOCTYPE html> <html lang="en" xmlns="http://www.w3.org/1999/xhtml"> <head>     <meta charset="utf-8" />     <title>Licensing</title>     <script src="../../ClientGlobalContext.js.aspx" type="text/javascript"></script> <script src="https://mtcau.crm8.dynamics.com//WebResources/mtccc_XrmSvcToolKit.js" type="text/javascript"></script> <script type="text/javascript">     function openLicenseSolution() {         var url = Xrm.Page.context.getClientUrl();         var solFetchXml = "<fetch version='1.0' output-format='xml-platform' mapping='logical' distinct='true'>" +                         "<entity name='solution'>" +                         "<attribute name='uniquename' />" +                         "<attribute name='solut

what is Append and Append To?

A append B   -> appends B to A A appendto B   -> appends A to B For example:  When you attach a note to a case, you must have the Append access right on the note and the Append To access right on the case for the operation to work. on Case          form     Note lookup Append to                  Append          N              :          1          (Relationship)

USING WEB API REQUEST CREATE, UPDATE, DELETE, RETRIEVE, RETRIEVE MULTIPLE, ASSOCIATE, DISASSOCIATE

//////CREATE THE RECORD//////////////// var entity = {}; entity.new_currency = Number(parseFloat(13666).toFixed(4)); entity["new_customer_account@odata.bind"] = "/accounts(F62765A4-941A-E711-8117-C4346BDC5E51)"; entity.new_datetime = new Date("04/12/2017").toISOString(); entity.new_decimal = parseFloat(22.223).toFixed(2); entity.new_floatpoint = parseFloat(2.3215).toFixed(2); entity["new_lookuponaccountfromcontact@odata.bind"] = "/contacts(D9058775-01F0-E611-812C-5065F38C8781)"; entity.new_optionset = 1; entity.new_twooptionset = false; entity.new_wholenumber = null; entity.accountnumber = ""; var req = new XMLHttpRequest(); req.open("POST", Xrm.Page.context.getClientUrl() + "/api/data/v8.2/accounts", true); req.setRequestHeader("OData-MaxVersion", "4.0"); req.setRequestHeader("OData-Version", "4.0"); req.setRequestHeader("Accept", "a

Fetch XML versus Query Expression Microsoft Dynamic CRM

Fetch XML versus Query Expression Query Expression : A query expression is used to search for records for a single   entity type. Queries are built as an object model. This class supports all  the features in FetchXML except for aggregates and grouping. It also supports   both early and late bound entity programming styles. Query Expression can only be used in server side language i.e C#. Query Expression is class based and is easy to use, although you can only query one entity type at a time.  Therefore, if you need to get data from a parent entity, such as a contact, and then get data from a child entity, such as a custom product entity, you have to perform two queries.  First you must retrieve the contact to get access to its attributes, then you must retrieve the product using the contact id that links the contact to the product.  With Query Expression, you can specify the attributes you want returned, or indicate you want all attributes returned, you can specify “and”

Append and Append To difference in Microsoft Dynamic CRM

Append:  When an entity has the lookup of another entity on its form. It is important that the user have the “Append” privilege on this entity so that it can set the values for the lookups on this entity. For eg: Contact has the lookup of Account on its form so here the user needs to have the “Append” privilege to be able to set the parent account. Append To:  When an entity is available as a lookup on another entity form. It is important that the user have the “Append to” privilege on the entity that is referred to in the lookup so that it can set the values for the lookups of this entity on any other form. For eg: Account has the lookup of primary contact. So here the user needs to have the “Append To” privilege to be able to set the Primary Contact for the Account. Append and Append To basically deal with the entities that are parties to a 1:N relationship or N:1 relationship. This post is CRM security 101, but I get asked this question fairly often, so it seems that there