User Profile
richrich123
Helper III
Joined 6 years ago
User Widgets
Contributions
Re: Drill Through query
bhanu_gautam Thanks fo your suggestion, it makes sense but I dont think it fits the problem, possibly me not explaining well enough. Table = PhoneCalls Table = Appointments Table = Emails Table = DateTable (mainly for using Month and QTR to report on) Report = Phone Calls - Chart showing Calls by Month + PhoneCallData report (drill down report) Report = Appointments - Chart showing Appointments by Month + AppointmentData report (drill down report) Report = Emails - Chart showing Emails by Month + EmailData report (drill down report) So the common field DateTable(Month) is used on the X-Axis of PhoneCall, Appointment and Email reports so when you go to PhoneCall and drill, you see all 3 when all I want to see is the Phone Call Data drill through Hope that makes more sense762Views0likes1CommentDrill Through query
Afternoon, I have a 2 user reports, phone call data and revenue data. I also use a date table with both so I can see chart data by month. I have 2 further hidden reports phonedata and revenuedata which are used for drill through so users can see a table of the data behind the chart. Because both my phone call and revenue reports display charts based on month, it means I have to add the same MonthName from the date table to the drilldown fields on both phonedata and revenuedata reports So when you right click and drill through on the phone call data or revenue reports, you see the drill report option for both phonedata and revenuedata which is confusing for the user Is there a way when you can restict the drill down report so on the Phone report you only see the phonedata drill down report (and vice versa for revenue). Seems a bit shortsighed if you had 10 reports and 10 reports with drill down data and all are based on dates and use the same month/Qtr chart that when ou drill you have to see 9 other irrelevant drilldown options and have to find the right one. ThanksSolved830Views0likes3CommentsRe: Preview.Error: The type of the current preview value is too complex to display
I did the same as a test, just took the users table as a single entity. Also tried with just case resoultion entity and the same. This was why I raised a ticket with MS becuase I couldn't see how/why it can be a relationship issue with only a single table but they have said that is the case and it relates to all the relations that exist from the table, even if you arent getting/using the others and the only way around it is to edit the M code to limit your columns initially and then add more in which I have ended up doing using the M query tool in xrmtoolbox. Not idea as it did take seconds and now it takes much more messing about just to get a simple table10KViews0likes0CommentsRe: Preview.Error: The type of the current preview value is too complex to display
Outcome from the MS support team was that there are too many relatioships. Seems a bit odd as our tables such as users are just standard Dynamics tables and nothing has changed for a long time but anyway. In the end they suggested creating the connection and edditing the M code to limit the number of relationships. Example M code: let Source = Sql.Databases("LAPTOP-IDOG6CV8"), AdventureWorks = Source{[Name="AdventureWorks"]}[Data], dbo_DatabaseLog = AdventureWorks{[Schema="dbo",Item="DatabaseLog"]}[Data], #"Removed Columns" = Table.RemoveColumns(dbo_DatabaseLog,{"PostTime", "XmlEvent"}) in #"Removed Columns"10KViews1like0CommentsRe: Preview.Error: The type of the current preview value is too complex to display
I have a case open with MS on this. Just done an hour with an engineer, unable to get a resoltion as yet after the session, he has gone to further investigate. Will uopdate when I get a resolution.11KViews0likes0CommentsRe: Preview Error
Anonymous , Im not familar with TRF as suggested in that post but either way, I cant see rolling back will help me becuase if I create a brand new PBI and just get the users or case table, it still gives this error as soon as I select the table and hit the transform button.805Views0likes0CommentsPreview Error
Hi, Since I upgraded to latest version, I am getting preview errors on multiple tables, was fine before. I have seen a few other people have started getting this since upgrade but none of the items suggested have resolved this. On one table (Dyanmcs (Incident Resolutions), I am only pulling 5 columns. I need to edit my fields under 'removed columns' but can't as I am getting the error "we cannot modify this step becasue there is are error steps, please resolve those errors first Im also getting the same problem with the systemusers table. Some others are fine. I tried disabling this as was suggested on another post but didn't help: Thanks881Views2likes2CommentsRe: Preview.Error: The type of the current preview value is too complex to display
I have just run into the same issue. I have multiple PBI's that all use the dynamics systemuser table and never had an issue. I have just upgraded PBI destop to latest version this morning and gone to create a new report. Added 3 tables, 2 came in fine, users is refusing to let me preview/transform/edit. I also dont seem to be able to do ctrl or Shft and select multiple columns to delete what I don't need.11KViews0likes0Comments
Data Privacy
Microsoft Fabric Community and Privacy
To learn more about how we manage your data, please review the Microsoft Fabric Community Data Privacy guide.