1 min readfrom Microsoft Excel | Help & Support with your Formula, Macro, and VBA problems | A Reddit Community

How do I do have multiple conditions for data validation in a table?

Our take

To set up data validation for your Excel table that ensures a "Submit Date" is both after the "Open Date" and that the corresponding project number starts with the "PROJ" prefix, you can use a custom formula. In the data validation settings, you can create a formula that combines these two conditions. For the "Submit Date," use `=AND(Log[SubmitDate]>INDIRECT("Log[OpenDate]"), LEFT(Log[Proj#], 4)="PROJ")`. This will guide users to submit valid project numbers while ensuring the correct date sequence.

In the world of data management, the ability to enforce rules and guidelines is crucial for maintaining integrity and accuracy. This is particularly true when dealing with project tracking in spreadsheets, where multiple conditions for data validation are often necessary. A recent inquiry from a user seeking assistance with Excel highlights the complexities that can arise when trying to implement such conditions. The user’s case involves tracking project timelines, needing to ensure that the submission date follows the opening date and that the project number begins with the "PROJ" prefix. This scenario echoes common challenges faced by many users who strive for clarity and efficiency in their data management processes, a theme that resonates with discussions in our related articles, such as Job has me doing a needlessly complicated task.

The request for help reflects a broader trend in spreadsheet usage where users often feel overwhelmed by the complexity of their tasks. In this instance, the user has already begun to implement data validation rules but is stumped by the dual requirement for both date conditions and prefix validation. This situation underscores the importance of accessible and intuitive tools in spreadsheet technology. As users navigate through their workflows, they seek solutions that empower them to implement sophisticated logic without diving deep into technical jargon. This is where modern AI-native spreadsheet tools can play a transformative role, offering features that simplify these tasks through user-friendly interfaces.

Moreover, this inquiry shines a light on a key aspect of data management: the intersection of functionality and user experience. While the focus may often be on technical capabilities, the real value lies in how these capabilities serve the user. The frustrations expressed by the user in seeking help are not uncommon; many users desire systems that not only facilitate complex validations but also enhance their productivity without adding layers of complexity. This is an important consideration as organizations continue to adopt new tools and technologies. The focus should remain on how these innovations can streamline processes and improve user outcomes, as seen in other discussions such as Anthropic reinstates OpenClaw and third-party agent usage on Claude subscriptions — with a catch.

Looking ahead, the evolving landscape of data management will likely see increased integration of AI and machine learning, which can offer intuitive solutions to complex problems like the one presented here. As these technologies advance, they may provide users with tools that not only simplify data validation but also anticipate user needs and adapt accordingly. This evolution invites a question worth pondering: How will future innovations shape the way we interact with data, ensuring both precision and ease of use? As we explore these possibilities, it’s clear that the user experience must remain at the forefront of design and functionality in spreadsheet technology. By focusing on empowering users and streamlining their workflows, we can foster an environment where data management is not just a task but a means of unleashing creativity and productivity.

I made an excel database, formatted as a table. The intent is to track how long a project is in the idea stage and then how long the project takes to get to the kick off stage:

https://preview.redd.it/5kwv6ekeo7yg1.png?width=210&format=png&auto=webp&s=bafbce2702829d1a9c33ef935280ab95faa71f19

Proj# OpenDate SubmitDate
IDEA2 3/24/26
PROJ45 2/24/26 4/15/26
PROJ24 12/24/25 4/1/26

When a project is submitted to the committee (the SubmitDate) it gets a project number, denoted by the prefix PROJ. Here's the problem I have. I need to restrict the Submit Date to be both AFTER the Open Date AND have the "PROJ" prefix in Proj# column. (When an Idea is submitted, the user just overwrites the IDEA to PROJ.) For the data validation I have been using the date validation greater than or equal to =INDIRECT("Log[OpenDate]") but I have no idea how to account for the prefix issue. Can anyone help? Thank you.

submitted by /u/AnonAMouse100
[link] [comments]

Read on the original site

Open the publisher's page for the full experience

View original article