# Create account instead of modify **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** webservice-connector, sailpoint-identity-security\ **Created:** [October 16, 2024, 6:55am UTC](https://developer.sailpoint.com/discuss/t/create-account-instead-of-modify/85579 "2024-10-16T06:55:03Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![kani](https://avatars.discourse-cdn.com/v4/letter/k/85f322/32.png) [@kani](https://developer.sailpoint.com/discuss/u/kani)\ **Post date:** [October 16, 2024, 6:55am UTC](https://developer.sailpoint.com/discuss/t/create-account-instead-of-modify/85579/1 "2024-10-16T06:55:03Z")
Hi All, I have a target source AB and configured two webservice (A and B) sources for that target source in IDN using the account filtering. The accounts are based on the job title and aggregated into two separate sources. There are some identies that can be in both the sources. When an identity from source A requests the access for source B, instead of modify , create operation is triggered and its getting failed. how to handle this. ---
**Author:** ![Abhinov7](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/abhinov7/32/13253_2.png) [@Abhinov7](https://developer.sailpoint.com/discuss/u/Abhinov7)\ **Post date:** [October 16, 2024, 8:31am UTC](https://developer.sailpoint.com/discuss/t/create-account-instead-of-modify/85579/2 "2024-10-16T08:31:30Z")
Hi, As the account is not already available for the user in IDN for source2 It will definitely try to create account. Can you elaborate more on usecase? Somehow you can handle it via rule. -Abhinov ---
**Author:** ![KRM7](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/krm7/32/2685_2.png) [@KRM7](https://developer.sailpoint.com/discuss/u/KRM7)\ **Post date:** [October 16, 2024, 8:42am UTC](https://developer.sailpoint.com/discuss/t/create-account-instead-of-modify/85579/3 "2024-10-16T08:42:41Z")
Hi @kani Ya, this is a common use case but not that highly used in real-time. Since you don’t have account already in IDN for that source, so by default it will be create account only. - Develop a WSBO (Webservice Before Operation Rule) for Create Account operation. - You need to check if account already exists or not in your target application - How do you check if account already there or not ? You don’t need to develop code for that, Get-Object operation will be enough. - If it is not there then no change, create operation - If account is there then you need to change your request end point. Cheers Krish ---
**Author:** ![kani](https://avatars.discourse-cdn.com/v4/letter/k/85f322/32.png) [@kani](https://developer.sailpoint.com/discuss/u/kani)\ **Post date:** [October 16, 2024, 8:48am UTC](https://developer.sailpoint.com/discuss/t/create-account-instead-of-modify/85579/4 "2024-10-16T08:48:13Z")
Hi @abinov, Identity ABC is having an source A and in the target system AB. If ABC requests access from Source B. Error will say " email already exist" . Becase both the sources are from the target same source. Provisioning from both the source A and B will trigger in target system AB. Account filter based on job is used create these two sources . Can we check the attribute value of job and change the create operation to modify? ---
**Author:** ![Abhinov7](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/abhinov7/32/13253_2.png) [@Abhinov7](https://developer.sailpoint.com/discuss/u/Abhinov7)\ **Post date:** [October 16, 2024, 8:54am UTC](https://developer.sailpoint.com/discuss/t/create-account-instead-of-modify/85579/5 "2024-10-16T08:54:52Z")
> [@kani](#): > > and in the target system AB. If ABC requests access from Source B. Error will say " email already exist" . Becase both the s Hi, Yes in before operation rule you can check if the account exists on target and change the baseURL in the rule. -Abhinov ---
**Author:** ![schattopadhy](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/schattopadhy/32/8854_2.png) [@schattopadhy](https://developer.sailpoint.com/discuss/u/schattopadhy)\ **Post date:** [October 16, 2024, 10:21am UTC](https://developer.sailpoint.com/discuss/t/create-account-instead-of-modify/85579/6 "2024-10-16T10:21:23Z")
@kani You can use a before operation rule to tap on operation type and check the account if available or not and based on that change the operation type. ```auto type accountRequest.setOperation(AccountRequest.Operation.modify)or paste code here ``` ---
**Author:** ![kani](https://avatars.discourse-cdn.com/v4/letter/k/85f322/32.png) [@kani](https://developer.sailpoint.com/discuss/u/kani)\ **Post date:** [October 17, 2024, 4:43am UTC](https://developer.sailpoint.com/discuss/t/create-account-instead-of-modify/85579/7 "2024-10-17T04:43:15Z")
Hi all, Is there any way to this without Before Operation Rule. There is configuration parameter skipGetObjectINCreate. Can we do something with this. What is the purpose of this attribute ---
**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\ **Post date:** [December 16, 2024, 4:43am UTC](https://developer.sailpoint.com/discuss/t/create-account-instead-of-modify/85579/8 "2024-12-16T04:43:18Z")
Closed on December 16, 2024, 4:43am UTC This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.