# Issues with --specified-id

**URL:** <https://forum.dfinity.org/t/issues-with-specified-id/20111>\
**Category:** Developers\
**Created:** [May 20, 2023, 7:51pm UTC](https://forum.dfinity.org/t/issues-with-specified-id/20111 "2023-05-20T19:51:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![lastmjs](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/lastmjs/32/3406_2.png) [@lastmjs](https://forum.dfinity.org/u/lastmjs)\
**Post date:** [May 20, 2023, 7:51pm UTC](https://forum.dfinity.org/t/issues-with-specified-id/20111/1 "2023-05-20T19:51:25Z")

</div>

I am running into a few issues with `--specified-id`. First off, it would be nice if `--specified-id` could be set in the `dfx.json` for an individual canister, so that the command line option would not be necessary.

Also I’m running into an issue where if I use `--specified-id` for some canisters, but then try to simply deploy another canister without `--specified-id`, I am getting the error `Canister be2us-64aaa-aaaaa-qaabq-cai is already installed`.

It seems like dfx is not appropriately finding new canister ids if the id is already taken by another canister.