Skip to main content
Liquid error: Exception has been thrown by the target of an invocation.

Vote (0) Share
's profile image

on

Comments (0)
's profile image Profile Picture

vu phung dang long on 18 Feb 2025 02:49:49

RE:

just make it like Excel :v

's profile image Profile Picture

Adrian John LADANIWSKYJ on 18 Feb 2025 00:44:57

RE:

Overall, The way reservations work in D365 BC is way more complicated that it needs to be. There really is no need for reservations to be linked to the individual item ledger transactions that make up the sum of the inventory that is on hand, as all the items of a particular item and lot number combination should be identical to each other. It really does not matter which particular bin the stock gets picked from, because it's all the same. A simple reservation ledger that adds and subtracts reservations, tagged to particular item numbers and lots is all that is needed, with the system simply summing up the entries to determine whether there is, or isn't any available (unreserved) stock. The sheer unnecessary complexity of how reservations work has caused huge headaches for our vendor partner, and considerable development expense for my organization.

's profile image Profile Picture

Meenakshi Raut on 17 Feb 2025 21:11:53

RE:

It's in the section where you can put people email ids, to whom you want to send the report. Sometimes the requirements are to CC and BCC few ids in the email while you are sending it out

's profile image Profile Picture

Danika LaBella on 17 Feb 2025 20:51:33

RE:

How does this need more votes? This plus the merged idea have over 15 THOUSAND votes.

's profile image Profile Picture

Joe Guidera on 17 Feb 2025 20:41:27

RE:

Consider the following Two of three query within the dataflow are valid and can be executed. The third is not valid (currently has one or more errors) and cannot be executed (perhaps due to a source API error that a vendor needs to resolve). That means you are unable to publish the dataflow, nor can it execute for the two valid queries since the third is not in a valid state.Today I have only one option, delete the query and all of the transformation steps and then re-create after it is possible to do so. I would prefer the option to "disable" that query and its transformations which would allow me to successfully publish and execute the two valid queries within the flow. Then when corrections are possible I enable and edit (as required) the invalid query to make it valid again and publish/execute as normal.

's profile image Profile Picture

Todd Chittenden on 17 Feb 2025 20:18:13

RE:

My Lakehouse is in a Display Folder. I open the lakehouse. I create a new Notebook. That notebook gets saved in the ROOT Folder of the Workspace.PLEASE make this easier for the users!!!

's profile image Profile Picture

Yihua Chen on 17 Feb 2025 20:04:21

RE:

I don't understand why this simple feature is not available after 7, 8 years.It's really painful if you have hundreds columns/fields to be added into one table visual.

's profile image Profile Picture

Brian Ellis on 17 Feb 2025 16:52:08

RE:

It is ridiculous that this hasn't been addressed yet and Microsoft hasn't responded to it or acknowledged it. It is the single most annoying feature in PowerBI. The worst part is, I don't even use or care to use Q&A. Essentially every time this pops up we are being forced to close out of a visual that we may or may not even use. What good are these forums if its been brought up time and time again and it hasn't been acknowledged

's profile image Profile Picture

Maximilian Zweydorff on 17 Feb 2025 16:47:53

RE:

Storm-2372 conducts device code phishing campaignhttps://www.microsoft.com/en-us/security/blog/2025/02/13/storm-2372-conducts-device-code-phishing-campaign/#Update-February-14I think it's finally time to change this!

's profile image Profile Picture

Wynne Barnes on 17 Feb 2025 16:19:09

RE:

Please set an option to specify font size, color and so forth, we should also be able to specify other options such as:* Bold* Italic* Underline* StrikeoutThe administrator marked this as completed on 3.09.2022, stating this functionality was introduced as of November 2021.This is NOT a functionality in Power BI. Please someone help with this idea!!!