search all users in a group (hundred users)

Has anybody used UAPI.PowerList to search all users in a specific group? There are hundred users in this group. On the first page, there 30 users ( which last name starting from A to

on the first page and they looked ok. But when I clicked "More" button to get more users, instead of all other users, I only got partial user list of this group.By the way, I have Form, webForm, esign installed on my system.Can anybody help? Thanks.Here is the codes://test r._ug_targetType = UAPI.GROUP r._ug_groupID = 87135 //// where 87135 is the group id of the group I'm testing.//test ugdata = UAPI.PowerList( prgCtx.USession().fSession, \ r._ug_targetType, \ r._ug_searchType, \ r._ug_searchValue, \ r._ug_action, \ r._ug_rowsRequest, \ ( isAuthority || isSigningGroup) ? UAPI.NAME : r._ug_searchColumn, \ r._ug_searchOpr, \ r._ug_startID, \ r._ug_startValue, \ r._ug_groupID, \ spaceID )Best Regards,Cecilia

Find more posts tagged with

Comments

eLink User

Message from Carsten Kulms via eLinkYou stumbled over a bug of the UAPI.PowerList function (LPAD-12729). The bug also affected LAPI's ListUserGroup function (LPO-468, afaik LAPIhas been fixed in 9.7.0)There exists a different function you may use. Unfortunately thatfunction is not documented nor do I know whether it is intended forpublic use.Please contact Open Text customer support to find a solution for youruse case. (Please note the two issue ids above or a link to this threadin your request.)

Cecilia_Qian

Thank you very much for your help. I'll contact Opent Text support for his issue.Cecilia

Louis_Routhier

Where can we get a description of these bugs?And to be quite honest, I'm starting to get qui annoyed by this little line "it is corrected in LL version ..." where you may replace [...] by "the version you actually don't have, will need weeks if not months to test, PS to install, and a headache for weeks to come"... I would not mind if the upgrade process was straight forward but even internally at OT, noone agree on a safe and recommended way of doing an upgrade! That's a shame and I think as clients (I think I speak for myself here and probably other LL administrators/programmers), we can't always be working on upgrading!Sorry... I had to release the pressure...

eLink User

Message from Carsten Kulms via eLinkSorry, afaik descriptions of these issues are not publicly available.Both are only indirectly mentioned in the "Livelink ECM - EnterpriseServer SDK Version 9.7.0 Release Notes":----8<--------8<--------8<--------8<----Problems Fixed in LAPI Version 9.7.0[...]2. The LAPI ListUserGroup function no longer uses UAPI.Powerlist asLivelink no longer uses it. Instead of Powerlist, LAPI should use$WebUser.PowerListPkg.GetUsers(), making sure to set PowerListPkgproperties before calling GetUsers(). (LPO-359)----8=--------8=--------8=--------8=----Please understand that I am not in the position to comment any further.I have taken the liberty to forward your comments.(I have to stress it once more: I am neither a member of the customersupport nor the LAPI/LES development team. With respect to LAPI and/orLES (OScript) development I'm in a similar position as you are.)

Bob Ulrich

Message from via eLinkI agree with your sentiments and would add one more pet peeve:In an earlier message on this thread someone said "descriptions of theseissues are not publicly available".I'm completely fed up with having to find every bug, quirk and specialfeature myself. I would really like for OT to proactively notify it'scustomers of these matters as soon as they are known internally. Bob Ulrich, PM USA Livelink Solutions Delivery Manager Internal: 8-283-9998, External: (804) 283-9998, Pager: (888) 489-4261 -----Original Message-----From: eLink Discussion: Development Discussion[mailto:development@elinkkc.opentext.com] Sent: Monday, February 12, 2007 10:14 AMTo: eLink RecipientSubject: Where can we get a description of these bugs?Where can we get a description of these bugs?Posted by Routhier, Louis on 02/12/2007 10:11 AMWhere can we get a description of these bugs?And to be quite honest, I'm starting to get qui annoyed by this little line"it is corrected in LL version ..." where you may replace [...] by "theversion you actually don't have, will need weeks if not months to test, PSto install, and a headache for weeks to come"... I would not mind if theupgrade process was straight forward but even internally at OT, noone agreeon a safe and recommended way of doing an upgrade! That's a shame and Ithink as clients (I think I speak for myself here and probably other LLadministrators/programmers), we can't always be working on upgrading!Sorry... I had to release the pressure...[To reply to this thread, use your normal E-mail reply function.]============================================================Topic: search all users in a group (hundred users)https://knowledge.opentext.com/knowledge/llisapi.dll/open/10881831Discussion: Development Discussionhttps://knowledge.opentext.com/knowledge/llisapi.dll/open/786303Livelink Server:https://knowledge.opentext.com/knowledge/llisapi.dllTo Unsubscribe from this Discussion, send an e-mail tounsubscribe.development@elinkkc.opentext.com.

Louis_Routhier

Thank you for the information. This will allow me to build a similar function based on it that would be able to return deleted users. When I get it to work, I'll try to post it here.

Louis_Routhier

I second

bkqc

The list would probably be too long

Quoted Bob Ulrich on 06/07/2016 11:03 AM:

Message from via eLink I agree with your sentiments and would add one more pet peeve: In an earlier message on this thread someone said "descriptions of these issues are not publicly available". I'm completely fed up with having to find every bug, quirk and special feature myself. I would really like for OT to proactively notify it's customers of these matters as soon as they are known internally. Bob Ulrich, PM USA Livelink Solutions Delivery Manager -----Original Message----- From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com] Sent: Monday, February 12, 2007 10:14 AM To: eLink Recipient Subject: Where can we get a description of these bugs? Where can we get a description of these bugs? Posted by Routhier, Louis on 02/12/2007 10:11 AM Where can we get a description of these bugs? And to be quite honest, I'm starting to get qui annoyed by this little line "it is corrected in LL version ..." where you may replace [...] by "the version you actually don't have, will need weeks if not months to test, PS to install, and a headache for weeks to come"... I would not mind if the upgrade process was straight forward but even internally at OT, noone agree on a safe and recommended way of doing an upgrade! That's a shame and I think as clients (I think I speak for myself here and probably other LL administrators/programmers), we can't always be working on upgrading! Sorry... I had to release the pressure... [To reply to this thread, use your normal E-mail reply function.] ============================================================ Topic: search all users in a group (hundred users) https://knowledge.opentext.com/knowledge/llisapi.dll/open/10881831 Discussion: Development Discussion https://knowledge.opentext.com/knowledge/llisapi.dll/open/786303 Livelink Server: https://knowledge.opentext.com/knowledge/llisapi.dll To Unsubscribe from this Discussion, send an e-mail to unsubscribe.development@elinkkc.opentext.com.

AKropp

Hi Folks,

In case you weren’t aware – and it may not be immediately obvious unless you spend a lot of time looking at the knowledgebase – but for at least the past year (and probably a bit longer) we’ve had a mandate to make sure that every bug we log gets an associated KB article. The previous message about the info not being available is WAY out of date.

Random example of one that’s still under investigation:

https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=62721180&objAction=ArticleView&viewType=1

Of course there may be some that fall through the cracks – we’re human after all – but it’s a far sight better than it once was! You can always subscribe to the knowledgebases you’re interested in to get mailings of all new articles that get posted. The release notes and Cumulative Update readme files are also excellent places to see lists of bugs that we’ve fixed for any given release (and if you’re on an older update – perhaps ones that you’d be interested in directly).

Cheers,

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Tuesday, June 07, 2016 11:18 AM
To: eLink Recipient
Subject: RE Where can we get a description of these bugs? 2

RE Where can we get a description of these bugs? 2

Posted by Routhier, Louis On 06/07/2016 11:03 AM

The list would probably be too long

Quoted Bob Ulrich on 06/07/2016 11:03 AM:

Message from via eLink I agree with your sentiments and would add one more pet peeve: In an earlier message on this thread someone said "descriptions of these issues are not publicly available". I'm completely fed up with having to find every bug, quirk and special feature myself. I would really like for OT to proactively notify it's customers of these matters as soon as they are known internally. Bob Ulrich, PM USA Livelink Solutions Delivery Manager -----Original Message----- From: eLink Discussion: Development Discussion [mailto:development@elinkkc.opentext.com] Sent: Monday, February 12, 2007 10:14 AM To: eLink Recipient Subject: Where can we get a description of these bugs? Where can we get a description of these bugs? Posted by Routhier, Louis on 02/12/2007 10:11 AM Where can we get a description of these bugs? And to be quite honest, I'm starting to get qui annoyed by this little line "it is corrected in LL version ..." where you may replace [...] by "the version you actually don't have, will need weeks if not months to test, PS to install, and a headache for weeks to come"... I would not mind if the upgrade process was straight forward but even internally at OT, noone agree on a safe and recommended way of doing an upgrade! That's a shame and I think as clients (I think I speak for myself here and probably other LL administrators/programmers), we can't always be working on upgrading! Sorry... I had to release the pressure... [To reply to this thread, use your normal E-mail reply function.] ============================================================ Topic: search all users in a group (hundred users)https://knowledge.opentext.com/knowledge/llisapi.dll/open/10881831 Discussion: Development Discussionhttps://knowledge.opentext.com/knowledge/llisapi.dll/open/786303 Livelink Server:https://knowledge.opentext.com/knowledge/llisapi.dll To Unsubscribe from this Discussion, send an e-mail tounsubscribe.development@elinkkc.opentext.com.

[To post a comment, use the normal reply function]
Topic:	search all users in a group (hundred users)
Forum:	Content Server Development Forum
Content Server:	Knowledge Center