So to be clear you are saying.. whenever you need to get a value from a dynamic tag within an expression its best to build the dynamic tag in a custom property first and then read the custom property with an expression.
I dont believe I have had to do that yet but I will keep it in mind.
Not sure, I don't know how your data is structured. Working through something similar in my head, I would probably skip the markdown component all together in favor of a flex repeater, but again, I don't know the details.
Almost, it is better to create a custom property with an indirect tag binding and then reference that property wherever you need it.
For example, say I do have a popup, where the station id is going to be used as a filter.
I would create a view parameter on the pop-up, and then create a custom property with an indirect tag binding which referenced that parameter.
All that being said this:
Sounds like a maintenance nightmare. I would far prefer having a single project/provider with each Station having it's own dedicated structure beneath it (perhaps even a UDT). This way any change would be automagically pushed out to all stations and there would not be any copy/paste or jumping through each provider project to "replicate" changes.
I always try to make my future self's life easier.
It will be but there are only about 12 machines or so. The issue is that these operator screens need to be unique to each station as they are recording job times. Unless I have fundamentally misunderstood something about how ignition works I dont know how two operators could be looking at the same 'record time' screen with two different sets of information on it. theyd just be overwriting eachothers information. Even if I added some dropdown to dynamically bind tags the dropwdown would change for all operators viewing the screen.
This is exactly the type of thing that session properties are for. If you do things correctly keeping session things tied to individual sessions then it is absolutely possible for two operators to be looking at the same 'record time' screen with two differnt sets of information.
I think I'm just gonna throw my computer away now... 
I will have to look into this more because I was under a totally different impression. I guess the good news is I can change this as I havent rolled any of this out yet.
