Hi Kim/Kelly,

I think this would be a great conversation to get feedback from R&D. Posting
a topic in the SolEx forum would ensure that you get feedback from OpenText
employees who don't regularly visit this group (Jian =).

-Emily

On Fri, Sep 16, 2011 at 2:39 AM, Markus Giesen <[email protected]>wrote:

> I like shortcuts and this is certainly a time saver if you know
> exactly what you're doing, thanks Kelly!
>
> However, from what I know this would make your RedDot installation
> warranty invalid.
> In other words: Touch the database and you'll lose the warranty for
> OpenText CMS.
>
> I can understand that it may seem like a good idea doing this but you
> never know what happens in the background in other columns in the DB
> and I've seen projects disintegrate over time because they have been
> changed in the database directly.
>
> Hearing the opinion of an RedDot engineer from the R&D team would be
> good on this.
>
> On Sep 13, 8:45 am, Jian Huang <[email protected]> wrote:
> > Kelly, as usual, another quality post.
> >
> > Just want to mention an alternate solution using existing tool without
> > DB access and possibly voiding warranty.
> >
> > Download RQLConsole fromhttp://www.solutionexchange.info/RQLConsole.htm
> >
> > Import, activate, and assign plugin to project.
> >
> > Use this RQL to list all File folders (File folders and Asset
> > Manager).   530.htm from RQL Documentation has more information.
> >
> >   <PROJECT>
> >     <FOLDERS action="list" foldertype="0" />
> >    </PROJECT>
> >
> > Copy the RQL results into Notepad++ to extract folder GUIDs
> >
> > Repeat the following code for N folder GUIDs
> >
> >   <PROJECT>
> >     <FOLDER action="save" guid="[!guid_folder!]"
> >      name="" path="[!path_folder!]" />
> >  </PROJECT>
> >
> > Paste all of the code into RQLConsole.  Yes, RQL can run in batch.
> >
> > On Sep 12, 6:02 pm, Kelly <[email protected]> wrote:
> >
> >
> >
> >
> >
> >
> >
> > > I should add this is in Management Server 10.1 SP2.
> >
> > > On Sep 12, 5:00 pm, Kelly <[email protected]> wrote:
> >
> > > > Just passing this on if helpful: the quickest way to update all your
> > > > Asset Manager paths - globally across your project- is definitely to
> > > > update the path within the database directly. I was able to update
> > > > about 100+ asset manager folders in 10-15 minutes total.  It would
> > > > have taken me much much longer had I used the reddot smart tree
> > > > interface.
> >
> > > > To do so, you must have access to your database (I'd suggest backing
> > > > it up first of course!).
> >
> > > > Under your PROJECT_NAME database, look for the table called IO_FDR.
> >
> > > > The column "FDR8" within IO_FDR table holds the asset manager path
> for
> > > > every asset manager folder in that project.
> >
> > > > A query like this will let you line up the FDR8 column neatly and do
> a
> > > > quick copy/paste replace on each entry within SQL:
> >
> > > > SELECT     TOP (200) FDR0, FDR1, FDR2, FDR3, FDR4, FDR5, FDR6, FDR7,
> > > > FDR8, FDR9, FDR10, FDR11, FDR12, FDR13, FDR14, FDR15, FDR16, FDR17
> > > > FROM         IO_FDR
> > > > ORDER BY FDR8
> >
> > > > I'm sure there's a query that would spare us the tedious manual copy/
> > > > paste replace job here but I was too lazy to write one :)
> >
> > > > At any rate, it saved a good deal of time off updating every folder
> > > > via the RedDot Interface.
> >
> > > > HTH,
> > > > Kelly
>
> --
> You received this message because you are subscribed to the Google Groups
> "RedDot CMS Users" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/reddot-cms-users?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"RedDot CMS Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/reddot-cms-users?hl=en.

Reply via email to