

Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2016-06-21
09:09
294 views
Designer changing GCV:s
Anybody else notice that sometimes for no good reason Designer decides
that the GCVs have changed?
For example if I have a GCV definition containing a number of <item>
elements Designer sometimes decides to change them to <item
xml:space="preserve"> when doing a deploy!
Also it sometimes adds a tmpId to every element!
that the GCVs have changed?
For example if I have a GCV definition containing a number of <item>
elements Designer sometimes decides to change them to <item
xml:space="preserve"> when doing a deploy!
Also it sometimes adds a tmpId to every element!
7 Replies


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2016-06-21
09:18
alekz wrote:
> Anybody else notice that sometimes for no good reason Designer decides
> that the GCVs have changed?
> For example if I have a GCV definition containing a number of <item>
> elements Designer sometimes decides to change them to <item
> xml:space="preserve"> when doing a deploy!
>
> Also it sometimes adds a tmpId to every element!
Thought the tempID was due to editing the GCV in iManager.
Definitely seen the xml:space="preserve" issue though.
> Anybody else notice that sometimes for no good reason Designer decides
> that the GCVs have changed?
> For example if I have a GCV definition containing a number of <item>
> elements Designer sometimes decides to change them to <item
> xml:space="preserve"> when doing a deploy!
>
> Also it sometimes adds a tmpId to every element!
Thought the tempID was due to editing the GCV in iManager.
Definitely seen the xml:space="preserve" issue though.
Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2016-06-23
12:21
alekz wrote:
> Anybody else notice that sometimes for no good reason Designer decides
> that the GCVs have changed?
> For example if I have a GCV definition containing a number of <item>
> elements Designer sometimes decides to change them to <item
> xml:space="preserve"> when doing a deploy!
Yes, very annoying, see this a lot, but totally random. Also sometimes it's a
@critical-change="true" being added/dropped after a package update. Oh, yes:
seems to be related to updateing packages, at least I have only seen it on a
compare after up/downgraing packages.
And now filters build from resources somethimes (but not always) get a
@priority-sync="" added...
--
http://www.is4it.de/en/solution/identity-access-management/
> Anybody else notice that sometimes for no good reason Designer decides
> that the GCVs have changed?
> For example if I have a GCV definition containing a number of <item>
> elements Designer sometimes decides to change them to <item
> xml:space="preserve"> when doing a deploy!
Yes, very annoying, see this a lot, but totally random. Also sometimes it's a
@critical-change="true" being added/dropped after a package update. Oh, yes:
seems to be related to updateing packages, at least I have only seen it on a
compare after up/downgraing packages.
And now filters build from resources somethimes (but not always) get a
@priority-sync="" added...
--
http://www.is4it.de/en/solution/identity-access-management/
______________________________________________
https://www.is4it.de/identity-access-management
https://www.is4it.de/identity-access-management


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2016-06-23
12:50
Great - I mean that I'm not the only one. 😛
On 2016-06-23 13:21, Lothar Haeger wrote:
> alekz wrote:
>
>> Anybody else notice that sometimes for no good reason Designer decides
>> that the GCVs have changed?
>> For example if I have a GCV definition containing a number of <item>
>> elements Designer sometimes decides to change them to <item
>> xml:space="preserve"> when doing a deploy!
>
> Yes, very annoying, see this a lot, but totally random. Also sometimes it's a
> @critical-change="true" being added/dropped after a package update. Oh, yes:
> seems to be related to updateing packages, at least I have only seen it on a
> compare after up/downgraing packages.
>
> And now filters build from resources somethimes (but not always) get a
> @priority-sync="" added...
>
On 2016-06-23 13:21, Lothar Haeger wrote:
> alekz wrote:
>
>> Anybody else notice that sometimes for no good reason Designer decides
>> that the GCVs have changed?
>> For example if I have a GCV definition containing a number of <item>
>> elements Designer sometimes decides to change them to <item
>> xml:space="preserve"> when doing a deploy!
>
> Yes, very annoying, see this a lot, but totally random. Also sometimes it's a
> @critical-change="true" being added/dropped after a package update. Oh, yes:
> seems to be related to updateing packages, at least I have only seen it on a
> compare after up/downgraing packages.
>
> And now filters build from resources somethimes (but not always) get a
> @priority-sync="" added...
>


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2016-06-23
13:49
On 6/23/2016 7:21 AM, Lothar Haeger wrote:
> alekz wrote:
>
>> Anybody else notice that sometimes for no good reason Designer decides
>> that the GCVs have changed?
>> For example if I have a GCV definition containing a number of <item>
>> elements Designer sometimes decides to change them to <item
>> xml:space="preserve"> when doing a deploy!
>
> Yes, very annoying, see this a lot, but totally random. Also sometimes it's a
> @critical-change="true" being added/dropped after a package update. Oh, yes:
> seems to be related to updateing packages, at least I have only seen it on a
> compare after up/downgraing packages.
>
> And now filters build from resources somethimes (but not always) get a
> @priority-sync="" added...
I think that priority sync came with 4.5. I expect some of this is DTD
validating.. I have seen it as well.
> alekz wrote:
>
>> Anybody else notice that sometimes for no good reason Designer decides
>> that the GCVs have changed?
>> For example if I have a GCV definition containing a number of <item>
>> elements Designer sometimes decides to change them to <item
>> xml:space="preserve"> when doing a deploy!
>
> Yes, very annoying, see this a lot, but totally random. Also sometimes it's a
> @critical-change="true" being added/dropped after a package update. Oh, yes:
> seems to be related to updateing packages, at least I have only seen it on a
> compare after up/downgraing packages.
>
> And now filters build from resources somethimes (but not always) get a
> @priority-sync="" added...
I think that priority sync came with 4.5. I expect some of this is DTD
validating.. I have seen it as well.


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2016-06-23
13:53
On 06/23/2016 06:49 AM, Geoffrey Carman wrote:
>
> I think that priority sync came with 4.5. I expect some of this is DTD
> validating.. I have seen it as well.
Priority Sync came out with eDirectory 8.8 a decade or whatever ago. Out
of Band Sync came with IODM 4.5.
--
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
>
> I think that priority sync came with 4.5. I expect some of this is DTD
> validating.. I have seen it as well.
Priority Sync came out with eDirectory 8.8 a decade or whatever ago. Out
of Band Sync came with IODM 4.5.
--
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2016-06-23
13:58
ab wrote:
> On 06/23/2016 06:49 AM, Geoffrey Carman wrote:
> >
> > I think that priority sync came with 4.5. I expect some of this is
> > DTD validating.. I have seen it as well.
>
> Priority Sync came out with eDirectory 8.8 a decade or whatever ago.
> Out of Band Sync came with IODM 4.5.
Still think it is dtd validation (pity the DTD is woefully incomplete)
> On 06/23/2016 06:49 AM, Geoffrey Carman wrote:
> >
> > I think that priority sync came with 4.5. I expect some of this is
> > DTD validating.. I have seen it as well.
>
> Priority Sync came out with eDirectory 8.8 a decade or whatever ago.
> Out of Band Sync came with IODM 4.5.
Still think it is dtd validation (pity the DTD is woefully incomplete)
Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.


Knowledge Partner
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2016-06-23
14:46
On 6/23/2016 8:53 AM, ab wrote:
> On 06/23/2016 06:49 AM, Geoffrey Carman wrote:
>>
>> I think that priority sync came with 4.5. I expect some of this is DTD
>> validating.. I have seen it as well.
>
> Priority Sync came out with eDirectory 8.8 a decade or whatever ago. Out
> of Band Sync came with IODM 4.5.
Yes. agreed. However, whoever in the IDC developed it, forgot that
Proirity Sync was taken as a name and the XML uses it, but the pretty
name is OOB Sync.
> On 06/23/2016 06:49 AM, Geoffrey Carman wrote:
>>
>> I think that priority sync came with 4.5. I expect some of this is DTD
>> validating.. I have seen it as well.
>
> Priority Sync came out with eDirectory 8.8 a decade or whatever ago. Out
> of Band Sync came with IODM 4.5.
Yes. agreed. However, whoever in the IDC developed it, forgot that
Proirity Sync was taken as a name and the XML uses it, but the pretty
name is OOB Sync.