A common moment in technical work is needing time from someone who knows far more than you do, often an SME. It could be someone from a different team, or someone just more experienced than you. Reaching out to them for more information or help is a basic part of the job. But a crucial part of it is figuring out how to give that person enough context to answer at the right level.
I don't think the answer is to pretend you understand more than you do. On the other hand, walking into the conversation with no framing at all can make it more difficult for both people. The other person has to guess what you know and whether to start with the basics or skip ahead.
A small amount of research beforehand can change the quality of the conversation. Sometimes that just means looking up the process or reading through an old ticket first. If there's a previous example, that can help too. The point isn't to solve the whole thing alone. It's to get yourself far enough that the conversation can start somewhere more useful.
What helps next is being clear about what you already understand. Something as simple as: "I looked through the old ticket, and I think I follow the general process. What I still need help with is understanding where this field is being populated from". That gives the expert something specific to respond to. It also makes it easier for them to meet you where you are, instead of oversimplifying or giving far more detail than you need.
This is also where good judgment comes in. Do enough groundwork that the conversation doesn't begin at the very first basic question, but don't wait so long that you spend hours circling on your own.
In cross-functional work, that kind of preparation can save time on both sides. It helps the other person explain the right thing, and gives you a better chance of leaving with an answer you can actually use.