Anonymous_User Absent Member.
Absent Member.
287 views

DNQuery Control Pseudo Greyed


So I have a DN Query control on my form, and if I click the browse
button it shows me a pop up list of users, but I cannot click on the
users.

The field actually appears disabled, but I have set the properties on
the field to enabled and even done a field.enable(). No joy.

Where is my knowledge gap here?

thanx
Rob


--
rrawson
------------------------------------------------------------------------
rrawson's Profile: https://forums.netiq.com/member.php?userid=403
View this thread: https://forums.netiq.com/showthread.php?t=48059

Labels (1)
0 Likes
10 Replies
Anonymous_User Absent Member.
Absent Member.

Re: DNQuery Control Pseudo Greyed


I am going to charge back NetIQ for hair restoration. This was caused by
the name of the field having a space in it.

PLEASE If you shouldn't put a space in the name of the field, just
disallow it in Designer. Or fix the controls so they work even if there
is a space in the name. Stuff like this makes a good product look bad.


--
rrawson
------------------------------------------------------------------------
rrawson's Profile: https://forums.netiq.com/member.php?userid=403
View this thread: https://forums.netiq.com/showthread.php?t=48059

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: DNQuery Control Pseudo Greyed

On 06/26/2013 07:34 PM, rrawson wrote:
>
> I am going to charge back NetIQ for hair restoration. This was caused by
> the name of the field having a space in it.
>
> PLEASE If you shouldn't put a space in the name of the field, just
> disallow it in Designer. Or fix the controls so they work even if there
> is a space in the name. Stuff like this makes a good product look bad.
>
>

Greetings Rob,
Before you blame the product, please double check your Designer
Set-up. Because when I create a field that has a space in the name (for
example: A Space) and try to deploy it, the deployment fails for
validation reasons. Here is the error from Project Checker:

"Field name 'A Space' in form 'request_form' contains illegal character(s)."

So, please double check that you have not disabled Validation Checking
during deployment.

Window -> Preferences -> Novell -> Provisioning -> Import/Deploy ->
Deploy Tab

"Allow deployment of objects with validation errors"

Is that checked or not?


Also, make sure you are not using the "evil" option of Compare. As you
should know by now, Compare does not perform any validation checking.
So if you perform a Compare -> update eDirectory you have skipped all
validation checking and just updated eDirectory with who knows what.

--

Sincerely,
Steven Williams
Lead Software Engineer
NetIQ
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: DNQuery Control Pseudo Greyed

On 06/26/2013 08:25 PM, Steven Williams wrote:
> On 06/26/2013 07:34 PM, rrawson wrote:
>>
>> I am going to charge back NetIQ for hair restoration. This was caused by
>> the name of the field having a space in it.
>>
>> PLEASE If you shouldn't put a space in the name of the field, just
>> disallow it in Designer. Or fix the controls so they work even if there
>> is a space in the name. Stuff like this makes a good product look bad.
>>
>>

> Greetings Rob,
> Before you blame the product, please double check your Designer
> Set-up. Because when I create a field that has a space in the name (for
> example: A Space) and try to deploy it, the deployment fails for
> validation reasons. Here is the error from Project Checker:
>
> "Field name 'A Space' in form 'request_form' contains illegal
> character(s)."
>
> So, please double check that you have not disabled Validation Checking
> during deployment.
>
> Window -> Preferences -> Novell -> Provisioning -> Import/Deploy ->
> Deploy Tab
>
> "Allow deployment of objects with validation errors"
>
> Is that checked or not?
>
>
> Also, make sure you are not using the "evil" option of Compare. As you
> should know by now, Compare does not perform any validation checking. So
> if you perform a Compare -> update eDirectory you have skipped all
> validation checking and just updated eDirectory with who knows what.
>

Greetings Rob,
One more thing, make sure that you are using Designer on a Supported
Operating System, because strange things can happen.

--

Sincerely,
Steven Williams
Lead Software Engineer
NetIQ
0 Likes
Knowledge Partner
Knowledge Partner

Re: DNQuery Control Pseudo Greyed

Steven Williams wrote:

> Also, make sure you are not using the "evil" option of Compare. As you
> should know by now, Compare does not perform any validation checking.


Is this documented anywhere? Does it affect UA contents only or
drivers/driverset alike?

At least
https://www.netiq.com/documentation/idm402/designer_admin/data/deploycompare.htm
l does not mention anything like that, but has: "You can run the Compare
feature at any time. If you choose to reconcile the differences between drivers
objects in Designer and eDirectory while in Compare, you won’t need to
separately run Import or Deploy to make the changes." Which kind of implies
Compare, Import and Deploy do the same thing.

And why should someone "know by now" (at least I didn't, even after using
Designer on a daily basis from when it was first released)? Get it changed. Why
is validation skipped on Compare, anyway?
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: DNQuery Control Pseudo Greyed

On 27.06.2013 09:25, Lothar Haeger wrote:
> Is this documented anywhere? Does it affect UA contents only or
> drivers/driverset alike?
>
> At least
> https://www.netiq.com/documentation/idm402/designer_admin/data/deploycompare.htm
> l does not mention anything like that, but has: "You can run the Compare
> feature at any time. If you choose to reconcile the differences between drivers
> objects in Designer and eDirectory while in Compare, you won’t need to
> separately run Import or Deploy to make the changes." Which kind of implies
> Compare, Import and Deploy do the same thing.
>
> And why should someone "know by now" (at least I didn't, even after using
> Designer on a daily basis from when it was first released)? Get it changed. Why
> is validation skipped on Compare, anyway?


I completely agree - compare should trigger any additional background
logic that Deploy triggers when it's determined appropriate.

I use compare out of habit outside of the Provisioning view.

--
----------------------------------------------------------------------
Alex McHugh
NetIQ Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support is provided via email.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: DNQuery Control Pseudo Greyed

On 06/27/2013 03:32 AM, Alex McHugh wrote:
> On 27.06.2013 09:25, Lothar Haeger wrote:
>> Is this documented anywhere? Does it affect UA contents only or
>> drivers/driverset alike?
>>
>> At least
>> https://www.netiq.com/documentation/idm402/designer_admin/data/deploycompare.htm
>>
>> l does not mention anything like that, but has: "You can run the Compare
>> feature at any time. If you choose to reconcile the differences
>> between drivers
>> objects in Designer and eDirectory while in Compare, you won’t need to
>> separately run Import or Deploy to make the changes." Which kind of
>> implies
>> Compare, Import and Deploy do the same thing.
>>
>> And why should someone "know by now" (at least I didn't, even after using
>> Designer on a daily basis from when it was first released)? Get it
>> changed. Why
>> is validation skipped on Compare, anyway?

>
> I completely agree - compare should trigger any additional background
> logic that Deploy triggers when it's determined appropriate.
>
> I use compare out of habit outside of the Provisioning view.
>

Greetings Alex,
As far as I know, Compare has never performed a Validation. I never
use it. Even if I am updating a Policy in a Null Driver, I will deploy
the entire Driver.
I would suggest that you log an Enhancement Request in the RMS
( http://www.novell.com/rms ) system to have Compare in Designer
changed to also perform validation



--

Sincerely,
Steven Williams
Lead Software Engineer
NetIQ
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: DNQuery Control Pseudo Greyed


Steve,

You are correct that I am running with validation turned off. I am
willing to accept that that is something I should be doing, but
validation is nearly unusable...with it turned on you get 4000+
irrelevant errors about localization that you must correct before you
can deploy anything successfully. I only speak English and my clients
are not interested in paying for me to localize a deployment for 18
languages that is only used in the 50 states.

<soapbox>
As far as the reason your experience with deploys versus out here in the
real world is different is something I have been saying for 20 years.
Software needs to be tested in and designed for sub-optimal
environments. I was intensely frustrated with Designer until I got my
SSD drive in my laptop (best $360 my company ever spent for me - thank
you Geoff for the suggestion). The real world does not have low latency
1000Mbit links everywhere. Last week I spent a week on site with a
client, which despite the challenges with the software, it was still
less frustrating in some ways because I was local to their server and
therefore deploys were really really quick. This week, however, I have
returned to reality, where my 6 Mb NATted link over a VPN through 17
router hops is the norm, and that kind of latency opens up windows for
all kinds of undesirable things to happen; it exposes where the
emperor's bits are hanging out.
</soapbox>

-Rob


--
rrawson
------------------------------------------------------------------------
rrawson's Profile: https://forums.netiq.com/member.php?userid=403
View this thread: https://forums.netiq.com/showthread.php?t=48059

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: DNQuery Control Pseudo Greyed

Rob,

the validator leaves a lot to be desired, but with filters you can focus
on the validation issues that are relevant to you.

Wolfgang


On 02.07.2013 15:54, rrawson wrote:
>
> Steve,
>
> You are correct that I am running with validation turned off. I am
> willing to accept that that is something I should be doing, but
> validation is nearly unusable...with it turned on you get 4000+
> irrelevant errors about localization that you must correct before you
> can deploy anything successfully. I only speak English and my clients
> are not interested in paying for me to localize a deployment for 18
> languages that is only used in the 50 states.
>
> -Rob
>
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: DNQuery Control Pseudo Greyed

On 07/02/2013 02:39 PM, Wolfgang Schreiber wrote:
> Rob,
>
> the validator leaves a lot to be desired, but with filters you can focus
> on the validation issues that are relevant to you.
>
> Wolfgang
>
>
> On 02.07.2013 15:54, rrawson wrote:
>>
>> Steve,
>>
>> You are correct that I am running with validation turned off. I am
>> willing to accept that that is something I should be doing, but
>> validation is nearly unusable...with it turned on you get 4000+
>> irrelevant errors about localization that you must correct before you
>> can deploy anything successfully. I only speak English and my clients
>> are not interested in paying for me to localize a deployment for 18
>> languages that is only used in the 50 states.
>>
>> -Rob
>>
>>

Greetings Rob,
To follow-up on Wolfgang's point. The first thing I do after
installing Designer (besides moving the Provisioning Tab up), is to
set-up a custom filter. I set it for Provisioning and to only report on
the following two:

1) Version Conflict
2) Error




--

Sincerely,
Steven Williams
Lead Software Engineer
NetIQ
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: DNQuery Control Pseudo Greyed

On 07/02/2013 09:54 AM, rrawson wrote:
>
> Steve,
>
> You are correct that I am running with validation turned off. I am
> willing to accept that that is something I should be doing, but
> validation is nearly unusable...with it turned on you get 4000+
> irrelevant errors about localization that you must correct before you
> can deploy anything successfully. I only speak English and my clients
> are not interested in paying for me to localize a deployment for 18
> languages that is only used in the 50 states.
>
> <soapbox>
> As far as the reason your experience with deploys versus out here in the
> real world is different is something I have been saying for 20 years.
> Software needs to be tested in and designed for sub-optimal
> environments. I was intensely frustrated with Designer until I got my
> SSD drive in my laptop (best $360 my company ever spent for me - thank
> you Geoff for the suggestion). The real world does not have low latency
> 1000Mbit links everywhere. Last week I spent a week on site with a
> client, which despite the challenges with the software, it was still
> less frustrating in some ways because I was local to their server and
> therefore deploys were really really quick. This week, however, I have
> returned to reality, where my 6 Mb NATted link over a VPN through 17
> router hops is the norm, and that kind of latency opens up windows for
> all kinds of undesirable things to happen; it exposes where the
> emperor's bits are hanging out.
> </soapbox>
>
> -Rob
>
>

Greetings Rob,
I deploy over a VPN a lot and do not experience anywhere near the
kinds of issues like I use to see with Designer 3.0.0. Designer 4.0.2
is a lot better in this area. I know that the team is still working on
improvements.

One major improvement dealing with the UAD is that ability to not import
the entire Role and Resource Catalog. This has helped a lot.


--

Sincerely,
Steven Williams
Lead Software Engineer
NetIQ
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.