Re: Any side effects when customise XSLs and ASPXs file by Matt
Matt
Fri Jan 14 10:54:59 CST 2005
I would agree.
The XSL files are generated when you publish changes from Deplayoment Manager.
At that point, the form code that is stored in the database is used to generate
the various XSL files that the app uses. You can modify these if you have
good change control procedures in place and remember that you will have to
re-modify them every time you publish.
The ASPX pages can be modified as well, but any patch or hotfix you install may
overwrite the file.
Neither of these types of changes are supported. The risk here is that if you
have a problem, it is possible that support will ask you to back out these
changes to verify the change isn't the cause of the problem.
Matt Parks
MVP - Microsoft CRM
----------------------------------------
----------------------------------------
On Fri, 14 Jan 2005 02:09:02 -0800, "Freek" <Freek@discussions.microsoft.com>
wrote:
As far as I know, this is not supported by MS. For aspx files, you can do
this without too much problems (although you should keep track very carefully
of what you've done for later upgrades). XSL files is another story. We
altered some of them to make fields read only etc, but when you redeploy
customization the XSL files are regenerated and all changed will have
disappeared. For me this came as quite a surprise, when all these little
tricks from our CRM consultant had suddenly disappeared. So if only for
maintenance reasons, I would not recommend altering XSL-files (unless someone
has found a new way to do this).
"Kim" wrote:
> Hi
>
> Any side effects when customise XSLs and ASPXs file directly from
> "C:\Program Files\Microsoft CRM\Tools\XslFiles"...this is in the CRM
> Server.....
>
> I will wait for answers before I modify the files directly.
>
> Thanks in advance.
>
> Kim.