@helen508light Did you have time to look into it?

Is the creation of a python template contemplated in the roadmap, like the one already present for R (rhtml)?

I began working through the RVisualTutorial last December, but have been unable to access it again since early January. Several links are now broken that previously pointed to github documentation on building custom visuals in R.

Does anyone know what happened and whether the documentation is still available somewhere?

Thank you!

@zBritva definitely helpful, thank you! I found a link in there that goes to the original tutorial I had found; it looks like someone forked it here: https://github.com/PowerBi-Projects/PowerBI-visuals/blob/master/RVisualTutorial/

@Aorus42 https://docs.microsoft.com/en-us/power-bi/developer/visuals/funnel-plot-from-r - is it the same?

It only happens when there is only one segment missing from the data.

• load a report with visual that can use the fetch more feature
• use the fetch more on the visual
• enter in edit mode
• change back to reading view

when changing back, the update sent on changing reading view contains the data that was originally loaded before using the fetch more. It also contains a segment object, meaning that fetch more can be called to get more data. Using fetch more now does not load any more data, even though the powerbi sent a segment object.

Calling fetch more does nothing at all, but returns with true.

I began working through the RVisualTutorial last December, but have been unable to access it again since early January. Several links are now broken that previously pointed to github documentation on building custom visuals in R.

Does anyone know what happened and whether the documentation is still available somewhere?

Thank you!

In PBI there is a provision to add page navigation on a button to navigate from one page to another page in a report. Is there a provision to achieve the same from a custom visual through formatting interface without using existing PBI buttons? If not would please plan to add this feature.

Hi- The issue still in latest API. Could anyone please update the status.

<br/>Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.<br/><br/>:x: snyk-bot sign now<br/>_{You have signed the CLA already but the status is still pending? Let us recheck it.}

<h3>Snyk has created this PR to fix one or more vulnerable packages in the npm dependencies of this project.</h3>

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • package.json
  • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	691/1000 <br/> Why? Recently disclosed, Has a fix available, CVSS 8.1	Prototype Pollution <br/>SNYK-JS-CACHEBASE-1054631	Yes	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

<details> <summary><b>Commit messages</b></summary> </br> <details> <summary>Package name: <b>webpack</b></summary> The new version differs by 250 commits.</br> <ul> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/610f36817af1f1c6929786d68f734ac582af1757">610f368</a> 5.0.0</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/5ce65c1ca3030a2d15a7988eac7a50a806eea539">5ce65c1</a> update examples</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/bbe12305d66c8ee2471a72b2806d94355511cc92">bbe1230</a> Merge pull request #11628 from webpack/bugfix/real-content-hash</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/75ecff262ef0c1953e0d13c0b6a06bdad7ccace5">75ecff2</a> 5.0.0-rc.6</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/bfc35d6fbe440ac36baa41f5ff5c5254eb8a8ae0">bfc35d6</a> Merge pull request #11603 from MayaWolf/master</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/76e8cbd91ff91aadb5637af4d8a34318f2e2a596">76e8cbd</a> Merge pull request #11622 from webpack/dependabot/npm_and_yarn/types/node-13.13.25</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/9fd1be2c114088d1dd4d9fdd9098196f455f4297">9fd1be2</a> chore(deps-dev): bump @ types/node from 13.13.23 to 13.13.25</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/36bcfaa149a47c01e7b92b23c03a4cf4bd5b3109">36bcfaa</a> Merge pull request #11621 from webpack/bugfix/11619</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/9130d10627bb1066c7c2eddd4a4aa4cbf83c6c43">9130d10</a> fix called variables with ProvidePlugin</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/3e42105df7938c7f160da4a325e156bd9cf09c8c">3e42105</a> Merge pull request #11620 from webpack/bugfix/11617</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/47097196bd0e9bf5ebad53a459cccd16edff16f7">4709719</a> skip connections copied to concatenated module</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/57b493f6ff0bd55dddfbfc7ffc2f2680a7f82a6d">57b493f</a> 5.0.0-rc.5</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/1658e2fd58e4c10f786bf04e22180d2ffa5ff1f1">1658e2f</a> Merge pull request #11618 from webpack/bugfix/11615</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/a8fb45d242537e380445c39957299674b15b6b7d">a8fb45d</a> fixes crash in SideEffectsFlagPlugin</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/84b196d32d886e99b934187027ddcc7b867d7981">84b196d</a> emit error instead of crashing when unexpected problem occurs</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/5573fed586aa3960794e8e4ad39f8766e3de88a4">5573fed</a> Merge pull request #11601 from Hornwitser/improve-suggested-polyfill-config</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/9b5cce931234ca284a79390450e0a43976b2fb08">9b5cce9</a> Merge pull request #11609 from snitin315/export-types</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/37c495c7ab0bdad8e13c02f32bdbef3c08e98610">37c495c</a> export type RuleSetUseItem</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/39faf340839791695ff543ce8b8d5ab53d328e41">39faf34</a> export type RuleSetUse</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/e5fd246353f314492c15d7eec6a149b342c4f72e">e5fd246</a> export type RuleSetConditionAbsolute</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/660baadbabb4e807f3238611096723b9021d03cd">660baad</a> export RuleSetCondition types</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/13e3ca57ba81ac9fcd98b189126658f11ce0f943">13e3ca5</a> Merge pull request #11602 from webpack/bugfix/shared-runtime-chunk</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/9c0587ec75b998bf18062029111da85855c468b6">9c0587e</a> Merge pull request #11606 from webpack/dependabot/npm_and_yarn/simple-git-2.21.0</li> <li><a href="https://snyk.io/redirect/github/webpack/webpack/commit/502d1666f42b70b5656fdf99ed472cd004f2395b">502d166</a> Merge pull request #11607 from webpack/dependabot/npm_and_yarn/acorn-8.0.4</li> </ul>

<a href="https://snyk.io/redirect/github/webpack/webpack/compare/71eb5931dbd7db125109a95692065333cea936a9...610f36817af1f1c6929786d68f734ac582af1757">See the full diff</a> </details> </details>

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information: <img src="https://api.segment.io/v1/pixel/track?data=eyJ3cml0ZUtleSI6InJyWmxZcEdHY2RyTHZsb0lYd0dUcVg4WkFRTnNCOUEwIiwiYW5vbnltb3VzSWQiOiI2NGZmNmQxNi1lNzUxLTRhNmMtOWE1MC0yNWYwMGFjYTlkYjgiLCJldmVudCI6IlBSIHZpZXdlZCIsInByb3BlcnRpZXMiOnsicHJJZCI6IjY0ZmY2ZDE2LWU3NTEtNGE2Yy05YTUwLTI1ZjAwYWNhOWRiOCJ9fQ==" width="0" height="0"/> 🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

Hi This bug has been fixed and will reach production by mid January. Thanks

When will this be implemented? Been requesting this feature to the team for more than 2 years now. I believe this is one of the most wanted features in Custom Visuals and it would enable loads of new and advanced scenarios.

I've tried it and it doesn't work without adding data to the bucket. If I add data to the columns bucket everything work fine, but we need it to work without data in the columns bucket. I also tried a lot of other combinations of subtotals, default values in subtotals, cloumns/no columns but no one worked the way we need to. There must be a way to only work with rows and rowSubtotals, have highlighting working and not include columns at all.

What I don't understand is, why it works in the development mode (pbiviz start) and breaks in the packaged visual.

Did you try to assign some column/bucket to columns of matrix. But without dataset. because using empty string looks strange

@zBritva thanks for looking in to it. I tried removing columnSubtotals, the highlighting works fine then, but I don't get any subtotals afterwards. What I except (and need) if I remove the columnSubtotals is that I still get the rowSubtotals, but I also don't get these.

I might be missing something else, but I dont know what it is..

@lucmax94 I checked your visual, Power BI fails on creating data aggregation for the visual, I see columnSubtotals in capabilities, but you don't use columns in matrix data view. Without columnSubtotals it works.

@helen508light did you already have time to look at it?

@helen508light I'm not able to share our source code with you, but I was able to repreduce this by creating a new visual and adding our capabilities (Not all of them). The source code and a report with some test data is attached.

I hope this helps and thank you for looking in to it!

Test Github.zip

@krngd2 It do works for https://github.com/microsoft/powerbi-visuals-gantt for example Could you please provide you capabilities.json? Maybe you have some issues with DataViewMapping usage in general

@lucmax94 Sounds strange, could you provide the source code?

No, I understood - it's best practice to use the script itself to check the fields requirements rather than dataviewmappings. max plays nice, min does not. I can't answer why, but the pbiviz devs seem content with the way it works as per this post.

Even if min worked as the docs indicate (I agree with you), checking inputs in your script is better from a usability standpoint. min's behavior is frustrating to an end user, as you have found, since there isn't an avenue of informing the user of the visual's input conditions explicitly with dataviewmappings. Printing an error using the visual script based on inputs met and unmet allows informing the user what they have wrong, and allows exerting more control over the input conditions required for the visual to display. The best way to move forward is to ditch min (it doesn't hurt to keep max ) and provide minimum input conditions in the visual's script.

I think we might not be talking about the same things. :) To clarify it, I've made a short clip: https://drive.google.com/file/d/1uXlgfZYfVCDowgLvoopW4igCfAycOJCV/view

I think it's not obvious that I had to fill back "Measure Data" first and then only I'm able to fill "Category Data".

As mentioned in the following post our visual does not work with the highlighting feature after we package the visual (pbiviz package). Everything works fine in the developer mode (pbiviz start). Is this a known issue, or are we missing something?

https://community.powerbi.com/t5/Developer/supportsHighlight-not-working-after-packaging-visual/m-p/1523090#M26625

Yeah, in practice you can really only have one min condition in total. If you have one, that category needs to be filled before any other. If you have two categories with a min, they both need to be filled, but each one prevents you from putting a field in the other. It essentially shoots itself in the foot. I would choose one or the other.

If you really want to enforce minimums for more than one category, I would suggest checking the presence of datafields in the visual's script and, if the minimum isn't met, printing a warning instead of any visual display. You can see this in practice in the rhtml funnel-plot tutorial

I forgot to mention that I'm using this Visual and I just extended the capabilities.json. https://github.com/microsoft/PowerBI-visuals-sampleBarChart