Update on this.
We tried importing the configuration settings into a brand new workspace of another machine and the settings were imported EXCEPT the compile commands we created. When I imported the same configuration file in my new workspace, the compile commands were included. Do note that I was the one who exported the configuration file to the network folder.
I'm not sure what triggers the missing compile commands after importing configuration settings or if it has something to do with the parent profile (??? I'm just guessing ???) which seem to be the same for all the workstations that we use.
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Fajardo, Eduardo
Sent: Tuesday, March 10, 2015 7:08 PM
To: WDSCI-L@xxxxxxxxxxxx
Subject: [WDSCI-L] RDi 9.1.1 Configuration files not updated after manual importing
I have created a set of preferences, compile commands and connections then exported them in a configuration file. The problem is that when we try to import this same configuration file to another user's workspace it just prompts the new settings as well as display the conflicting ones but after selecting/overriding what items to import the settings did not apply.
The (forced) push to client works which I was able to set up in test machine where I had sufficient authority but I can't do the same in our development machine so I had to resort to a manual configuration file.
Anyone encounter this? Is there any known limitations with importing configuration files into another user's workspace?
"Misys" is the trade name of the Misys group of companies. This email and any attachments have been scanned for known viruses using multiple scanners. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and Misys. Please refer to the executed contract between you and the relevant member of the Misys group for the identity of the contracting party with which you are dealing.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.
"Misys" is the trade name of the Misys group of companies. This email and any attachments have been scanned for known viruses using multiple scanners. This email message is intended for the named recipient only. It may be privileged and/or confidential. If you are not the named recipient of this email please notify us immediately and do not copy it or use it for any purpose, nor disclose its contents to any other person. This email does not constitute the commencement of legal relations between you and Misys. Please refer to the executed contract between you and the relevant member of the Misys group for the identity of the contracting party with which you are dealing.
midrange.com
