Well, before starting off with the post I must say that this is the pure development content most probably in the interests of developers? This is the multipart series in which I will be explaining how to handle the URL\u2019s to avoid navigation and other scripting issues in COM API development work. In this post I will be briefing an importance of passing parameters to the URL\u2019s and how to read them in pages efficiently to avoid crashing issues.<\/p>\n
I believe every developer developing the entity structures, ASP pages or even small scripts in CRM faces issues handling URL\u2019s back and forth through pages. For example if we are creating a standard entity in CRM it must be a thumb rule, that if I click on the record link in the list in list page and move to summary page the previous state has to be the list page only. I.e. if I click back button or continue button it should take me back to the list page. Similar is the case of Summary page. When summary page goes to edit mode, it\u2019s just a mode that changes so we don\u2019t need to handle the URL\u2019s in this case as explained, but still handle the several modes in the pages.<\/p>\n
When we are developing the entities we must make sure that we are always passing the primary id of the entity in all pages; specifically when I move from list to summary and there onwards to any other page related to the summary. For example suppose we have entity called Contracts which is a child entity of CRM Company entity we may put the tab named Contracts under Company context.<\/p>\n
![\"Custom](\"http:\/\/1.bp.blogspot.com\/_A6_b0zkYeSY\/TSb6KWBb7iI\/AAAAAAAABPY\/6eXbs1cTbuQ\/s1600\/clip_image002.jpg\")
<\/a><\/div>\n