Actually, we have met some users with the same situation as yours, and we are considering how to optimize for you guys.
here I am kinda torn where I would do those things, on one side i have access to pre and post scripts in Cases
but then I would use test scenario just as “bulk runner for cases”
i just think my mindset is still left in Postman
and not grasped the Test Scenario use cases in apidog 
I think it’s just difference in behaviour between Postman and Apidog
and since my mindset is still “stuck” in postman mode it’s probably just needs some adjustments and time
since I have just found out about apidog last week so I am still testing it out if it can cover my use cases that i had with Postman
So I guess my main confusion is where my logic should live, in APIs Cases or in Test Scenario steps
But I always found test plans/scenarios/execution runs to be kinda disposable things where you only check the reporting and execution runs
while the main logic is perserved toghether with API specification
for example it doesn’t make sense to me to have my pre and post JS scripts and assertions added to some scenario step where I would have to make sure it’s not deleted or the be reused etc. instead of just using it from Cases and maintaining it there.
But one can argue that like “APIs tab is for Devs and Test tab is for QA” so I would then just have smaller scenarios with JS scripts that would be re-used in a bigger scenarios and maintained only in 1 place but that kinda doesn’t go well in my brain organization 
it’s more of a dilemma “where do you plan to capture your functional checks logic” - APis cases or Test/Test Scenario steps
For now the “import from endpoing cases” as a reference works best for my needs, the only problem there is you are not able to check the values at glance for each step before you run your scenario
so you have to either go to edit or just run it and then check Actual Request tab
Which is fine for me I guess, only a few more actions
I completely understand your situation, and our suggested approach is to use endpoint cases for regression testing of individual endpoints (We will optimize related functionalities in the future, such as batch run cases and viewing request values in test steps directly, etc). For simulation testing of business scenarios, use test scenarios, as they can include process information.
Understood