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,  Thank you for adding to the explanation.  Here is a more thorough explanation.

 

License Exclusion is used in any scenario where a user account should not count against licensing.  That includes any person with multiple Windchill accounts (training, development, business configuration testing, dual-role administrators, etc.), and headless accounts used to connect PTC products to PTC products (e.g. publishing administrator).  Third-party integration accounts must be licensed.  Always follow up with PTC to ensure they haven't recently changed account licensing requirements.

 

Then there are scenarios where a user is a member of License Exclusion and a member of a 'PTC*' license group.  These need to be sorted out.

Most importantly, the OOTB site administrator account should NEVER be a member of any license group, including License Exclusion.  If it is returned in the report, it needs to be removed from all licensing.

 

Platform Structure has been deprecated for a while - replaced with PTC Platform Structures.  It still exists in Windchill systems and should not be in use, but we can't assume it doesn't still have users assigned to it.  If it is empty, it won't show in the results set.  If it is not empty, it's appearance in the results set prompts the report user to clean it up.

 

The full scenario wasn't fully explained.  Since the topic is reporting, the assumption is the requester is a site or organization administrator and may want to report on all license groups.  Our collective responses provide a level of report filtering.  Your response covers the license groups that pull a license.  My response expands to cover all license groups.  It is up to the reader to choose which is appropriate for their use case.

 

 

    Terms & ConditionsCookie settingsAccessibility statement