Every single day as a CRM Developer, one of my main concerns is in case of an exception is how to deal in the exception and save the information. Years ago, and with no CRM Online, our team was saving that information in a file, with our way of gathering the information (friendly message, message, level (low, high,..), type of exception (crm data access, plugins, workflows, java scripts, web extensions), stack trace, and all in a xml type form so we could easily check what was happening in the crm. However, everything changed when we start to implement in Online, we couldn’t use a file system approach, so we started to use an Entity for that purpose, with the same information, but because we were using an OO approach the only change was in one method only, and with this way we can use in both environments. What is your opinion?
top of page
Search
Recent Posts
See AllA user was trying to download a note attachment when the message "Invalid Action" just appeared in the browser. The first thing i did was using my old friend Diag Tool where i saw the exception "The k
10
Developer Extensions is a set of tools provided in the SDk that intendes to simplify and accelerate development. Usually to be used in Client apps, something like Portals. It provide the following cap
30
Not the best thing to do in terms of performance probably, but if you need to increase the max number of records per collection, i.e: Rest call to get records and render as a table in a custom page, b
30
bottom of page