Attribute name length limitation?

[FIMTooler]

Is there a character limit on the system name of an attribute?

I have both a 25 and 29 character length name for 2 attributes that are both booleans. When I search resources (with AttributesToGet, Unconstrained, or ExpectedObjectType), the attribute with the 29 character length is not returned, yet the 25 character length property is returned.

Using xPath to filter on the 29 character length attribute returns the correct number of objects with true\false values, yet the property itself is never listed.

Using Export-FIMConfig, the 29 character length attribute is returned.

Since it's not listed on the returned object, it cannot be modified.

[ryannewington]

I'm not sure I can explain this one. There isn't a limit on the attribute length. I've got plenty of > 25 char attributes in my environment

Can you give me some more specific steps to reproduce?

Is it a new schema attribute? You may need to restart the FIM service and restart PowerShell session in order to see newly created attributes, but that's the only reason I can think of for it not being seen. We do cache the schema to avoid expensive round-trips, and you have to invoke Update-ResourceManagementClientSchema to force a refresh.

[FIMTooler]

It probably is cached from existing powershell session as I usually disconnect from rdp keeping all the apps open.

I'll be able to verify in a couple of hours, but that seems to be the most likely scenario.

Thanks for the quick follow-up!

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Ryan Newington @.> Sent: Friday, April 23, 2021 8:04:45 PM To: lithnet/resourcemanagement-powershell @.> Cc: FIMTooler @.>; Author @.> Subject: Re: [lithnet/resourcemanagement-powershell] Attribute name length limitation? (#34)

I'm not sure I can explain this one. There isn't a limit on the attribute length. I've got plenty of > 25 char attributes in my environment

[image]https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F17229877%2F115940216-021ebe00-a4e4-11eb-9b98-eb781e96819f.png&data=04%7C01%7C%7Ccbef2073c22a4315a5c008d906b491ae%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637548194867158087%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=e5rSyu69rLHgHIPpHDVI%2F98kOhbQKz9zOA6AsLMGoQ8%3D&reserved=0

Can you give me some more specific steps to reproduce?

Is it a new schema attribute? You may need to restart the FIM service and restart PowerShell session in order to see newly created attributes, but that's the only reason I can think of for it not being seen. We do cache the schema to avoid expensive round-trips, and you have to invoke Update-ResourceManagementClientSchema to force a refresh.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flithnet%2Fresourcemanagement-powershell%2Fissues%2F34%23issuecomment-825998996&data=04%7C01%7C%7Ccbef2073c22a4315a5c008d906b491ae%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637548194867158087%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=YxcHty0rqPYY0NJ%2Fd3kRoFRffGlJ2Von5y97nnKVSmk%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHKBDSK4XI6PGHE4R3XAGB3TKIDJ3ANCNFSM43O4TKGA&data=04%7C01%7C%7Ccbef2073c22a4315a5c008d906b491ae%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637548194867168078%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=yneZL%2FJ6veO4whM8I1MiR45yD0dO3EA92z671oZmEWY%3D&reserved=0.

[ryannewington]

Ok great. Let me know how you go.

[FIMTooler]

It was the schema refresh. Once that was done it worked. Thanks again!