Web.Contents failed to get contents from 'https://ausreman.tidywork.com/api/materials' (400)
I have tried a number of scenarios for posting data, but I have come up with nothing. I am trying to write a power query that posts data to a REST API (https://ausreman.tidywork.com/api/materials), it posts data for materials. The current query I have is: = Json.Document(Web.Contents("https://ausreman.tidywork.com/api/materials",[Headers= [#"Authorization"="Basic ZZZZZZZZZZZZZZZZZ",#"Content-Type"="application/json"], Content=Json.FromValue({[projectId="65b6d1fe-ec2e-47c3-9c92-2aad8fdd1d26",userId="67220adb-d5cb-4667-a3ce-ebe3d6248334",materialDateUtc="2015-09-14T07:11:00",materialDate="2015-09-14T17:11:00",materialId="00000000-0000-0000-0000-000000000000",materialLocationId="1aeb9552-a3e9-4804-a7b2-641b290dac8d",materialItemCode="1H3338",materialItemId="f9be8264-81f0-4ae2-a12b-569b3e05d034",costCurrencyId="17709522-6b2e-4b01-9cdf-bb7eb0a43c52",chargeCurrencyId="17709522-6b2e-4b01-9cdf-bb7eb0a43c52",taskId="b2ffc2cf-326a-fc91-eb40-c4ddb4147a35",state="Approved",usageQuantity=1,quantity=1,cost=0.21,charge=0.25]})]), 1252) The only thoughts I had was that it had something along the lines of the size of the data being post. Please help me remove this frustration.
Rolling 4 hours average
Hi Experts, Add one more column "Rolling 4 hours Average", it has to map current row MIPS value + previous 3 , then divided by 4. we have a slicers to filter by region, by month, by date. after this "Rolling 4 hours Average" created, we have to calculate MAX MIPS value without 4 hours rolling by Month and MAX MIPS value with 4 hours rolling by month. I have tried the below DAX by result is not as expected. Rolling 4h Avg (strict ÷ 4) = VAR RelationDistinct = SUMMARIZE ( ALLSELECTED ( 'VW_MF_TRANSACTIONS' ), 'VW_MF_TRANSACTIONS'[LPAR], 'VW_MF_TRANSACTIONS'[MetricDateTime_1] ) VAR W = WINDOW ( -3, 0, RelationDistinct, ORDERBY ( 'VW_MF_TRANSACTIONS'[MetricDateTime_1], ASC ), PARTITIONBY ( 'VW_MF_TRANSACTIONS'[LPAR] ) ) VAR Sum4 = SUMX ( W, [MAX MIPS]) RETURN DIVIDE ( Sum4, 4 ) Please help to fix this asap. Thanks DK
How to programmatically publish Power BI / Power Query Dataflows after deployment (CI/CD scenario)?
Hi all, We are working on implementing CI/CD for Power Platform / Power BI across multiple environments (Dev → UAT → Prod), and we’ve run into a blocker related to publishing dataflows. 🔹 Context: We deploy solutions and artifacts using Azure DevOps pipelines Dataflows are successfully deployed to the target environment However, they remain in an unpublished state until manually opened and published in the UI 🔹 Issue: We are unable to find any supported way to programmatically trigger the “Publish” action for dataflows. 🔹 What we’ve tried: Power Platform CLI (pac) Power BI REST APIs Power Automate (cloud flows) Power Automate Desktop (UI automation approach — not ideal for enterprise pipelines) 🔹 Current limitation: There does not appear to be a supported API to: Publish Dataflow (equivalent to clicking "Publish" in UI) 🔹 Questions: Is there any supported API or mechanism to publish dataflows programmatically? Are there any recommended enterprise patterns for handling this in CI/CD? Is this capability on Microsoft’s roadmap (e.g., Fabric / Dataflow Gen2)? 🔹 Current workaround: We are currently considering: Manual publish step post-deployment Raising a Microsoft support ticket for confirmation #power-bi #dataflows #power-platform #ci-cd #azure-devops #fabric
Snowflake Dynamic M Query Parameter: "Query is too complicated to run" with 500+ items
Hello, I am encountering a critical issue with Dynamic M Query Parameters and Snowflake connectivity in Power BI Desktop. Scenario: DataSource: Snowflake (DirectQuery). Feature: A Mass Filter Slicer is bound to a List-type Parameter (PartNumber). Implementation: The parameter is used within a Value.NativeQuery block to filter a large fact table. The Problem: When users select a small number of items, the query folds and performs perfectly. However, once the selection exceeds ~400-500 items, the visual fails with the error: "This query is too complicated to run" Observations: I have confirmed that the SQL generated by the parameter creates a massive IN ('P1', 'P2'...) clause. I have tried using Text.Combine and Snowflake’s FLATTEN(SPLIT()) functions to pass the list as a single string, but I still hit complexity limits. Turning off EnableFolding is not an option as the base table contains millions of rows and causes a timeout. Question: Is there a known character limit for literal strings passed via Dynamic M Parameters in the Snowflake connector? Are there recommended patterns for "Semi-Joins" that maintain folding without bloating the Native Query SQL string? @#Snowflake, #DynamicMParameters, #QueryFolding, and #NativeQuery Any guidance from the community or the PG (Product Group) would be greatly appreciated.
