mirror of
https://github.com/Set-OutlookSignatures/Set-OutlookSignatures.git
synced 2026-04-26 18:55:53 +03:00
[GH-ISSUE #123] Issue with finding groups with spaces in their name? #54
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Set-OutlookSignatures-Set-OutlookSignatures#54
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @AndreDFC12 on GitHub (Aug 21, 2024).
Original GitHub issue: https://github.com/Set-OutlookSignatures/Set-OutlookSignatures/issues/123
Issue happens in the latest release
Previously solved issues and documentation
Code of Conduct
What happened?
I'm trying to use the group tag in my INI file, but whenever I include a group with a space in it's name, the program returns a "Not found" in the output. I've tried using our AD's netbios domain name and have also tried using AzureAD (we're a hybrid environment, but we solely use Exchange online). I have no issues querying any of the groups with no spaces in the names (with the netbios domain name), but have failed to query multiple of our groups with spaces.
I've also tried updating the display name (as that's another tag parameter) of the group to be it's name with no spaces, and that didn't seem to work either.
Any ideas?
@GruberMarkus commented on GitHub (Aug 21, 2024):
The problem has initially been reported and answered here: https://github.com/Set-OutlookSignatures/Set-OutlookSignatures/discussions/121#discussioncomment-10260032
The next release will contain a fix. In the meantime, you can correct it yourself by following the instructions in the link above.
Please let me know if this solves your problem.
@AndreDFC12 commented on GitHub (Aug 21, 2024):
Ah man, how did I miss that?! Thank you for pointing me in the right direction. I'll make the change in the script and update you. Do you have a sense of when the next release is expected?
@AndreDFC12 commented on GitHub (Aug 21, 2024):
That seems to have fixed it! Thank you!
@GruberMarkus commented on GitHub (Aug 21, 2024):
Hopefully within the next few weeks, but it could also be two months. I can't be more precise at the moment.
@GruberMarkus commented on GitHub (Aug 21, 2024):
My pleasure!