on
RE:
Quick heads up
We haven't spoken in a while, but I just saw a very negative opinon online about microsoft.com and thought it was important to email you guys to disprove this article.
It seems like there's some unfavorable news that could be harmful to your reputation.
Knowing how easily stories can get out of hand and not wanting you to be unprepared, I decided to notify you.
Here's the source of the info:
https://ibit.ly/Ye-kO
My hope is it's all a misunderstanding, but it seemed prudent you should know!
Best wishes,
Drew
RE:
Also have this need on a current project.It would be so much easier to fit reality.
RE:
Yes! Exactly what i am also looking for! Current functionality shows all the consumption item tracking lines that were posted on a production order. Functionality is needed to select which item tracking lines were used/consumed for a output posting. That way, item tracking shows only output specific tracking lines instead of all the ones used in the production order.
RE:
Thanks for taking the time to post this idea Erik! To me this is a no brainer that this should in fact be standard functionality!
RE:
Yes this feature will be really useful to use categories.
RE:
I think it used to support it, but the site has had XSS issues (there was a submission a while back that had a drive-by redirect to another page). There was also a bug where the idea summaries in search would just truncate the generated HTML, meaning closing tags were missed and randomly breaking the formatting of the site. The fix for these seems to have been slowly turning off features in the editor and now none of them work.
RE:
Any Update, when this can be LIVE
RE:
Team,Can this be priorities? As Service Principal not able to execute Fabric notebook, automation use case related to event based trigger using Azure Function can be achieved. Please help.
RE:
Existing workarounds like using DAX Studio or DAX Query View to evaluate DAX virtual tables cannot take the full Filter context of the actual report visuals into account (e.g. when the report uses table visuals, line chart visuals, etc. we cannot replicate the evaluation context for each data point easily in DAX Query View), and is therefore of limited usefulness.Many times, a better workarund is using the TOSCV workaround (https://www.linkedin.com/posts/brianjuliusdc_dax-daxprotips-buriedtreasure-activity-7154157526417108992-bChZ/) because this can be used inside a table visual, and therefore be exposed to the actual evaluation context (filter context) in the visual. However this is cumbersome and can make the visual difficult to read during debugging (e.g. due to limited formatting of the csv string, and size limitations).
RE:
We require this - our supervisors currently create (manually) stock movement work to request stock from our secondary warehouse. The operative processing this work should be able to overpick against this work