It looks like we don't have the translated page you're looking for, but we do have other content in English and offer support in English.
It looks like you're trying to figure something out.
Stuck or just want advice?
You can unlock the true value of Wrike in our Community
Connect with thousands of leading teams, learn best practices, and shape the future of the product. What are you waiting for?
Now other members can find, vote, and discuss your idea.
Our Community Team reads every suggestion (yes, every one) then compiles and shares the feedback with our Product Team. Happy posting!
More about Product FeedbackWhat can we help you with?
Learn. Share. Discuss.
Now other members can find, vote, and discuss your idea.
Our Community Team reads every suggestion (yes, every one) then compiles and shares the feedback with our Product Team. Happy posting!
More about Product FeedbackIt would be nice if, per folder/project, Wrike could support the concept of enforced unique values for custom fields. For instance, there are fields like PO Number, etc, which should only be used once - ideally, if the user entered a non-unique value into a form or a table which required unique values, Wrike would come back and provide an error/prompt to enter a unique value.
Folllowing List for Post: Allow Custom Fields to Require Unique Values
[this list is visible for admins and agents only]
Hi Alan Stone, welcome to the Community!
Thank you for sharing this suggestion, it's been passed on to the Product team.
Hi everyone!
We need something very similar.
We are collecting our invoices in Wrike. Each invoice is a task.
Every time if we receive an invoice we fill out a request form. In this form we have to fill the "invoice number" field.
We would like to avoid to duplicate invocies in Wrike. We can solve this problem, if Wrike could check one of the custom field and if it is equal to the new task we should have an alert.
I think the idea behind this is very similar. I hope you can find a solution for this problem.
Thank you for sharing your use case, Márton Gallai! If there are any changes here, I'll be sure to keep you posted.