web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Answered

Retroactively assigning Party ID to a worker

(2) ShareShare
ReportReport
Posted on by 92
Hello,

I have an environment in which I have created an assortment of workers and assigned them to a position. Each position in turn is added to a position hierarchy (under the relationships tab) which determines the approval flow in a 3rd party solution. 

Now, after having created all the setup (quite extensive) I have discovered that no party IDs were created for the workers, which prevents us from assigning a User to the person (that should be the same as the worker). 

Is there a way of retroactively creating party IDs and assigning them to a worker after the worker is already created? I would hope there is a way of avoiding having to create the workers again by creating a Party ID first and then creating a new employee from that.

Any input is appreciated. Thanks in advance,

Oskar
I have the same question (0)
  • Martin Dráb Profile Picture
    238,745 Most Valuable Professional on at
    This question is already discussed in a duplicate thread in Finance forum. If anyone wants to reply, please do it there, so we don't have two parallel discussions on the same question.
  • Verified answer
    ON-16052045-0 Profile Picture
    92 on at
    The whole issue was a misunderstanding. The users were created before this question was posted, they were assigned Party IDs. I was reacting to the fact that I could not connect a user to its corresponding worker (in the User forms), the list of possible workers to assign that matched the user seemed empty thus I concluded that there was no Worker/party ID in the system. 

    The real issue was that there were duplicates of users and the old version of the user was already associated with its corresponding worker, thus the worker/party ID was already "occupied". After ammending this by removing the worker connection to the old user (and subsequently deleting the old duplicate of the user) I could assign each user to its corresponding worker

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 545 Super User 2026 Season 1

#2
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 408

#3
Adis Profile Picture

Adis 267 Super User 2026 Season 1

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans