on
RE:
This is crazy. We cannot decide whether to print a label or not in a WMS system? Am I dreaming?
RE:
Can you please provide an update to this idea. Our users are requesting this heavily!
RE:
I cite David Carr's comment with the exact same wording:I'd like to see a robust UI where you can set up a "Environment Copy Template" that identifies the source (almost always prod) and the target (some sandbox), and enables you to select specific tables to copy data from, and more importantly identify tables you do NOT want to bring over. Ideally, for those specific tables copied, we'd be able to specify an advanced-find like/FetchXML based query that would identify the specific rows to copy (such as "Last 3 Months", e.g.). (It could also be a "solution-based" copy, where we create a solution that identifies the tables to copy.)We use lookups extensively, and hence have dozens of reference tables that need to copied to each environment. We have years of historical transactional data that does NOT. Today, because i have to copy the entire production data set, we spend days running bulk delete jobs and Power Automate flows to remove data in a copied environment. Very inefficient use of resources.
RE:
For enterprise deployment it is fundamental to support themes and templates in the Service. It is the only way to standardise report creation within large organisations.
RE:
This is a highly anticipated requirement, I would like to extend this to not only mask but also delete / leave data using this mapping.