AnsweredAssumed Answered

External Container relative path doesn't change when renaming files

Question asked by Kantala on May 21, 2013
Latest reply on May 21, 2013 by mikebeargie

I've created a set of 'framework' files to use as a starting point for development of different solutions.


I used the Developer Utilities to create a copy with a new name in order to start work on a new project. However, the 'relative to:' path in the Container storage tab of the field definitions hasn't changed. E.G, the main interface file of the blank 'framework' files is titled 'Modules' with an associated 'modules__Data' file. The path shown in the renamed copy is still '[database location]/Files/Modules/'.


I had assumed that using Developer Utilities to rename the files would strip out this relative location, but apparently not. Any new container fields that I create in these files also retain the 'Modules' in the file path.


Anybody come across this, and if so, did you manage to resolve it?







Screen Shot 2013-05-21 at 09.44.00.JPG