Hi Everyone,

My company recently updated Data Migrator to release 8203M and we are trying to allow the ETL development team to be working on different releases at the same time. To do this we created two different directories and copied the base synonyms into each directory. We have updated the app path for each developer to have the primary path be the release folder they are working on. The issue we are encountering is when a person working on the second release modifies a base synonym and tries to put it in the new flow we are receiving an error that the file cannot be used because a file with the same name already exists in the other directory. Is there a way to alter the search path for a user to so they can choose which directory they want to work in?

Thank you,

Dave

This message has been edited. Last edited by: FP Mod Chuck,

You can explicitly specify the application directory in your data flows. On the ribbon's Home tab click on Options and then in the Options dialog select Synonym Editor check the checkbox for "Use application directory name for synonym." You can do the same in Process Flow Designer if desired.

Otherwise you could change the order of the directories in the application path so it finds the desired one first.

By the way Release 7.7.09/8.2.05 is now generally available for download. I would recommend using the current production release.

Thank you Clif, I apologize about the delayed response. We have tried your suggestion and are still having some challenges. If I create a synonym under the directory Release 1 and then copy it down to release 2's directory the application path is still pointing to the Release 1 directory and any changes made in the Release 2 folder also impact the file in Release 1. Is there an option that when moved the synonym's app path can be updated to its current directory without having the rebuild each synonym each move?

Thank you,

Dave

Dave

I pinged Clif about this and he said you should open a case with techsupport. I may not understand your issue but the APP PATH is not dependent on a synonym it is independent and tells WebFOCUS the order in which to search for synonyms. You can adjust it to make Release 2's app folder in front of Release 1's app folder.

Thank you Chuck, We have had a ticket opened for a while and were offered similar suggestions as to what Clif suggested. Our open ticket is 190213043.

Thank you,

Dave

Dave

I looked at the case and you have the best customer service reps looking at this. I don't have anything else to offer you.

How about the development team using....

APP PREPENDPATH

I didn't 'test' this, but this seems to be the logical way to declare an app folder, when a file might exist multiple places.

Or you can have an -INCLUDE with the path statement.

I prefer using PREPENDPATH, because it leaves everything else in place.