Sunday, 8 December 2013

One custom view... Many Places....

Recently, I worked on a issue with custom view which caused a bit of pain to fix. I would like to share it with you guys...

A custom view was applied to a project template and all the project created from it had the same custom view copy in it. Now I wanted to fix a html section in this custom view which is easy. But what about all the project created from the project template which contains the copy of the old html file. I need to find them and add a version to the custom view.....not cool at all...

Anyways, to avoid such scenario in future a simple solution can be put into place.

1. Create a Folder and create the custom view here.
2. Give Public Access over the custom view (So that no permission issue)
3. Create shortcut in the project template pointing to the custom view.
4. Rename the customview shortcut in the project template as customview.html (This is important) and it good to hide the shortcut.

Now all the project created from the template will have the shortcut instead of new copy of custom view (we just saved a small amount of space too by avoiding creation of new copies). Also, any change to the custom view can be easily done by doing changes in just one place.

So, what do you think.....A neat solution in place right???