Scheduling a User Data Functions item directly fails every time with "FunctionName is null or empty"
Hi all, I'm running into an issue with the native Schedule option on a User Data Functions item (not the Data Pipeline Functions activity, the Schedule button on the UDF item itself). Every single scheduled run fails with: [{"errorCode":"WorkloadException","subErrorCode":"WorkloadException","message":"Invalid Argument: FunctionName. FunctionName is null or empty. Please provide a valid value"}] At first I thought this was because I had more than one function in the item and the scheduler didn't know which one to trigger, but I trimmed the item down to a single function and it still fails the exact same way. So it doesn't seem to be a "multiple functions" thing. What I did: Created a UDF item with one function, published it, tested it manually - works fine, returns the expected output. Set up a Schedule on the item and let it run for a while. Checked Monitor - every run failed with the error above. In the Monitor run details, both "Function name" and "Invocation ID" show up blank (--), so it really looks like the scheduled trigger just isn't passing a function name at all when it kicks off the run. Things I already tried: Deleted and recreated the schedule Reduced the udf to a single function Manual run of the function: works every time Calling the same function from a Data Pipeline Functions activity (where you explicitly pick the function in the activity settings) and scheduling the pipeline instead: works fine, no problems at all So the function itself is clearly not the problem, it's specifically the item-level Schedule that seems broken - it's just not sending FunctionName in the invocation request the way the Pipeline activity does. Anyone else seen this, or know of a fix/workaround? Happy to share invocation IDs or more logs if it helps.
Fabric UDF works in Test mode but fails when invoked on Run mode
Hi guys! I'm experiencing an issue with a Fabric User Data Function that works perfectly in the UDF Test experience, but consistently fails when invoked from a Power BI Report using a Translytical Task Flow or on Run mode. Scenario The function receives several parameters from the report and writes records into an Azure PostgreSQL database using psycopg2. The code executes successfully when I run it directly from the Fabric User Data Functions test interface. However, when the same function is triggered from a Power BI report or on Run mode, the invocation fails before I can identify the root cause. import datetime import fabric.functions as fn import logging import psycopg2 udf = fn.UserDataFunctions() @udf.function() def StatusAENovosRegistros( aeIdListaStr: str, produto: str, recorte: str, status: str, justificativa: str, comentario: str, nomeUsuario: str, economia: int, emailUsuario: str ) -> str: conn = psycopg2.connect( database="xxx-xxx-xxx", user="user", host="xxx-xxx-xxx-xxx", password="""xxxyyyvvv""", port=5432 ) cur = conn.cursor() aeIdLista = aeIdListaStr.split(",") for areaExpansao in aeIdLista: dados = ( areaExpansao, produto, recorte, status, justificativa, comentario, nomeUsuario, economia, emailUsuario ) cur.execute( """ INSERT INTO "SCHEMA".table ( ae_id, produto, recorte, status, justificativa, comentario, nome_usuario, economia, email_usuario ) VALUES (%s,%s,%s,%s,%s,%s,%s,%s,%s) """, dados ) conn.commit() cur.close() conn.close() return "Dados inseridos com sucesso" I always get the message below: { "functionName": "StatusAENovosRegistros", "invocationId": "00000000-0000-0000-0000-000000000000", "status": "Failed", "errors": [ { "errorCode": "WorkloadException", "subErrorCode": "NotFound", "message": "User data function: 'StatusAENovosRegistros' invocation failed." } ] }Choosing the Right Way to Run Python in Microsoft Fabric
Fabric gives us several ways to run Python, and at first they can look overlapping. In this post, I share the practical decision model I use to choose the right option based on execution mode, compute engine, and data access path. If you are code-first and want fewer wrong turns when moving from exploration to production, this guide is for you.
A Typo when collapsed the left panel in UDF (Korean)
Hi Team, When I collapsed left explorer window in the UDF, I noticed the title was upside down. That should be rotated as follows: I will submit a support ticket to support engineer team. https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket Korean English Thanks, Hong
