We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
CRM Version: V1.1.3
Steps To reproduce--
1. Log in as Admin/User. 2. Click on sources inside the settings tab. 3. Click on Create source button. 4. Create multiple source with the same name
Actual result: There is no warning if the user trying to create multiple sources with the same name. Please find the below screenshot.
Expected result: There should be an error if the user trying to create multiple sources with the same name.
The text was updated successfully, but these errors were encountered:
@Sanjaybhattwebkul,
The name can be the same as in the backend it is handled by id. If id is the same then it is a bug.
id
You can check the reference from the Attributes page section.
Attributes
Sorry, something went wrong.
@Sanjaybhattwebkul, The name can be the same as in the backend it is handled by id. If id is the same then it is a bug. You can check the reference from the Attributes page section.
@devansh-webkul There is no duplicate name in the attribute section. Please find the screenshot Here.
Click Here . to view the issue.
Issue krayin#471 fixed
67f662a
Merge pull request #612 from jitendra-webkul/master
530e3f0
Issue #471 fixed
No branches or pull requests
CRM Version: V1.1.3
Steps To reproduce--
1. Log in as Admin/User.
2. Click on sources inside the settings tab.
3. Click on Create source button.
4. Create multiple source with the same name
Actual result: There is no warning if the user trying to create multiple sources with the same name. Please find the below screenshot.
Expected result: There should be an error if the user trying to create multiple sources with the same name.
The text was updated successfully, but these errors were encountered: