on
RE:
Please vote this up!
RE:
When generating the SPED Fiscal file, the 0200 record is considering the Search name for the DESCR_ITEM fieldThe field highlighted in yellow searches for the Search nameItem number: BRMF710Product name: ATIVO - Ativo - parafusadeiras e rosqueirasSearch name: ATIVO - PARAFUSADEIR |0200|BRMF710|ATIVO - PARAFUSADEIR|||PCS|08|||84||||The field highlighted in green that should be considered in the text file (Product name)|0200|BRMF710| ATIVO - Ativo - parafusadeiras e rosqueiras|||PCS|08|||84||||
RE:
Would be really useful for one of my customers.
RE:
any update for this feature?
RE:
When using the focus mode the customer doesn't know that this option is available. unless clicking on the visual (e.g. Sankey diagram)
RE:
The inability for team-members to view flows without wrangling a service account or manually importing the .json flows slows down development and limits knowledge transfer (both decreasing the chance that the organization will actually make the most effective use of Fabric that it could).Pulled from my posting here:https://community.fabric.microsoft.com/t5/Data-Engineering/Collaboration-in-Dataflows/m-p/4193592#M4344
RE:
It would be great to have indeed this possibility in the software.You can't explain this to a customer that it is working on standard way and that this is not working when you have custom development.
RE:
As mentioned already, a basic function that is really needed
RE:
In this case (item end of life), we should even have an option at the product lifecycle that prevent the master planning to generate planned orders, but keeping the net requirements data accurate, so that planners can monitor how sales orders consume the stock until they can finally switch the product lifecycle of the item to Obsolete and therefore not be part at all of the MRP anymore.
RE:
Please...