Skip to main content
R
RK_114927095-Regular Member
5-Regular Member
January 23, 2026
Solved

User assigned license & last login report

  • January 23, 2026
  • 1 reply
  • 736 views

Using the attached QML, I was able to retrieve the users assigned to their respective licenses. However, the report is also returning the associated team roles along with the license or group names to which the licenses are mapped.

Do you have any suggestions on how to exclude all team roles from the report? Although the criteria section technically allows filtering out roles, it is not practical to identify every possible role and create separate criteria entries for each one.

Best answer by joe_morton

You'll have to update your report. Instead of reporting Users directly linked to the license group, you'll need to report users in a group in the license group. Ex: User -> Group -> License Group

 

Just keep in mind that once you make that update, the report won't return any information on a user who is directly assigned a license. Ex: User -> License Group

 

You'll also want to consider if you have subgroups. Ex: User -> Subgroup -> Main Group -> License Group

 

For the reporting to work, you may need to create several reports to cover all cases of license assignment that you use at your company. (Direct assignment, 1 level group, 2 levels groups)

 

The only other way (I know of) would be to create your own Java Method, and use that in your QML. That would be the way to have a single report that can recursively navigate group structures to get the final license assignment, regardless of how many group levels there may be.

1 reply

Fadel
Fadel23-Emerald I
23-Emerald I
January 26, 2026

try this ,I used a dummy trick , all license groups starts with PTC:

Fadel_0-1769431126586.png

 

 

Buiꓘa
M
mmeadows-316-Pearl
16-Pearl
January 26, 2026

FYI: To include all PTC license groups, including those not beginning with PTC (e.g. License Exclusion and Platform Structures), filter groups where their description includes the word 'license'.

mmeadows3_0-1769432835948.png

 

M
mmeadows-316-Pearl
16-Pearl
January 26, 2026

@Fadel FYI: I loaded your report in my Windchill 13.0 dev system and kicked the tires.

 

Notes:

1. The report complained that PrincipalType doesn't exist.  It doesn't prevent loading of the report in 13.0.

mmeadows3_0-1769436957687.png

That attribute was added in 13.1.    Just need to remove the attribute from the Select or Constrain tab before running the report in 13.0 or earlier.

 

2. Reports like this only work for direct user assignment to a license group.  It pointed out where my dev system still had users assigned to license groups we no longer have licensing to use.

 

3. Many larger implementations add users to user-defined (org) groups that are then added to the (site) license groups.  There could be one or several intermediate groups between the user account and the license group.  I don't recall if it is possible for query builder to recursively navigate group relationships to return users directly or indirectly associated to license groups.  It might be possible with a custom reporting class that recursively navigates groups until it identifies license groups.

 

It is a simple request, but the actual report isn't easy.  I'm not asking for a rewrite of the report.  Just sharing expectations for this kind of report.

    Terms & ConditionsCookie settingsAccessibility statement