Had the need today to backup some report definitions from a SQL Server Reporting Services 2005 Server prior to terminating it. I've linked and put it in pastebin as well.
Monday, April 29, 2013
Friday, April 19, 2013
CRM 2011: Mass Update Opportunity Estimated Closed Date
Today, I fielded a request from a collegue who was attempting to update large number of opportunities with the Bulk Edit feature. They were attempting to update the "Estimated Close Date" field.
I noticed what they had as well -- in the bulk edit form the field was disabled. I presume this is because behind the facade, this is a calculated field.
There's a quick and easy way to overcome this problem if you run into it. A simple dialog (or workflow) can still manipulate this field. The former can even be constucted so it prompts for a value.
I've included a screenshot tour of the dialog I constructed below:
I noticed what they had as well -- in the bulk edit form the field was disabled. I presume this is because behind the facade, this is a calculated field.
There's a quick and easy way to overcome this problem if you run into it. A simple dialog (or workflow) can still manipulate this field. The former can even be constucted so it prompts for a value.
I've included a screenshot tour of the dialog I constructed below:
Saturday, March 16, 2013
CRM 2011: Whole Number fields -- dropping the comma
I fielded a request today that involved a CRM field that was configured as a whole number that's intended to store the year component of a date. In the installation of CRM that I was working in -- numerics are formatted with commas.
The problem that the requestor wanted resolved was that 1995 was appearing in the UI as 1,995 -- they wanted to drop the comma.
I ran across a simple javascript one-liner here that solved the problem.
The author was quick to point out that the resolution would likely be consider unsupported. While this is true, I approach these as a measured risk. It worked for me.
The problem that the requestor wanted resolved was that 1995 was appearing in the UI as 1,995 -- they wanted to drop the comma.
I ran across a simple javascript one-liner here that solved the problem.
document.getElementById("fieldname").value = Xrm.Page.data.entity.attributes.get("fieldname").getValue();
The author was quick to point out that the resolution would likely be consider unsupported. While this is true, I approach these as a measured risk. It worked for me.
Subscribe to:
Posts (Atom)