"Visualization URL" error with Power BI frames

[janicedawley]

We just recently started receiving the following error when added/editing Power BI frames. We haven't changed anything on our end (still DisplayMonkey v.1.6.0.182), and this was working as recently as a couple of weeks ago. Any ideas on what's happening?

An error occurred while processing your request.

Source | Powerbi/Edit

Message | The field Visualization URL must be a string or array type with a maximum length of '200'.

The full stack trace is:

at DisplayMonkey.Models.DisplayMonkeyEntities.SaveChanges() at DisplayMonkey.Controllers.PowerbiController.Edit(Powerbi powerbi) at lambda_method(Closure , ControllerBase , Object[] ) at System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary2 parameters) at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary2 parameters) at System.Web.Mvc.Async.AsyncControllerActionInvoker.b39(IAsyncResult asyncResult, ActionInvocation innerInvokeState) at System.Web.Mvc.Async.AsyncResultWrapper.WrappedAsyncResult`2.CallEndDelegate(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.b3d() at System.Web.Mvc.Async.AsyncControllerActionInvoker.AsyncInvocationWithFilters.<>cDisplayClass46.b3f() at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult) at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>cDisplayClass21.<>cDisplayClass2b.b1c() at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>cDisplayClass21.b__1e(IAsyncResult asyncResult)

[moeman2323]

I am just setting up Display Monkey to test PowerBI on it and ran into the same issue. Have you found a solution for this?

Thanks,

Mike

[janicedawley]

I haven't. I frankly have no clue where to look. I'm guessing Microsoft changed something on their end, and DisplayMonkey needs to be updated to be compatible again. But I don't really know.

The weird thing is, our existing Power BI frames still work fine. But they can't be edited in DisplayMonkey, and we can't create new frames, either.

[moeman2323]

One of my developers was able to resolve the issue. I can't provide details because this is outside my area of expertise, but he had to decompile the code for website and add a get max syntax to the Powerbi model to resolve it. I'll try to get details and post it.

[janicedawley]

Hi Mike --

If you do have some more information you can provide, I'd really appreciate it. We have some in-house developers who might be able to assist us if we know what needs to be fixed.

-- Janice

[moeman2323]

Hi Janice,

I'm going to describe it to the best of my knowledge as my developer is very hard to get a hold of.

The issue is within the code and SQL database. The URL length for PowerBI is limited to 200 characters. I believe PowerBI is now using URLs that are longer than 200 characters.

We had to update the column Url in the Powerbi table in SQL to a higher amount (we used 500), and also uncompile the presentation dll (https://github.com/fuel9/DisplayMonkey/blob/master/Presentation/Powerbi.cs) and allow the powerbi code to allow Url to retrieve max characters, then recompile it.

[janicedawley]

Thanks, Mike! Armed with that information, I was able to engage one of our in-house developers, who was also able to fix it. He did have to edit one other DLL to get it working, though -- the DisplayMonkey.Management.dll. Ideally this would be fixed in the primary distribution of the code... but I'm not sure how the protocols work around that.

[psined1]

Hi, thanks everyone for contributing to find the solution to the issue. We'll have it added among other things to the next release shortly.

[rcashin]

Any more info on the changes you guys made before recompiling?

Any status on an update for the fix?

Thanks!

[psined1]

Planning to release fixes shortly. Please stay tuned. Thanks for your patience!