microsoft / powercat-code-components Goto Github PK

I am using trying to use the DetailList to list out the data from a sharepoint data source. And I found that there is no way to just access the properties in the collection, liked Requestor.DisplayName, compared to the Data Table control.

I am building a custom page where I am using the DetailsList. I am filtering the items of the DetailsList based on the selection of several comboboxes.

When I am building the app in in the maker studio the DetailsList is filtered as expected, and showing the items/records.

However, when I run custom page in the model-driven app, the item/records are not loading:

Are there any known limitations regarding this or is this a bug?

I can't select the column headers anymore if I am using a collection or Add Columns in my Items field.
If I am just using Dataverse it works fine.

For some reason, any added columns are "unselectable" even if the ColSortable is set to true.

To test this out
Items:
Table( {id: "1", name: "contoso" }, {id: "2", name: "MSoft" } )
columns_Items:
Table({ ColName: "id", ColDisplayName: "Name alt", ColWidth: 200, ColSortable: true, ColIsBold: true, ColResizable: true },{ ColName: "name", ColDisplayName: "Name", ColWidth: 200, ColSortable: true, ColIsBold: true, ColResizable: true } )

Column headers are unclickable

PowerApps version: 3.24032.26

This was working previously and has only recently happened.

On setting the column_items i was seeking guidance on how to set the color of a tag conditonal based on the input

{
ColName: "Response",
ColDisplayName: "Tag",
ColCellType:"tag",
ColWidth: 70,
ColTagColorColumn: "TagColor", // How to lets say if the value of the rendered cell was Hot, then i want to set the color to Red and so on?
ColTagBorderColorColumn: "TagBorderColor",
ColVerticalAlign: "Center",
ColHorizontalAlign:"Center",
ColResizable:true
}

Or is there a workaround i could use?

The standard textbox control has the ability to only update the output text property after a debounce delay controlled by the DelayOutput property.
This is important when performing searches as the user types to prevent events from being fired too frequently.

Icon Component does not have OnSelect

I can see the implementation here: onSelect at index.ts and also here: onClick prop on RenderButtonAs. But for some reason the prop is not present.

Used Version 1.0.19
Used on Canvas App

My fluent detail list is connected to sharepoint list. I am not finding a way to show display name of assigned user
It shows a messed up data instead

Hi. There are some translations that have long names instead of the short names and they don't render properly on the Calendar.

These are the problematic ones:

• bg-bg:
  
  Storybook here

• ca-es:
  
  Storybook here

• el-gr:
  
  Storybook here

• et-ee:
  
  Storybook here

• it-it:
  
  Storybook here

• lv-lv:
  
  Storybook here

• nl-nl:
  
  Storybook here

• pl-pl:
  
  Storybook here

• ro-ro:
  
  Storybook here

• sr-latn-rs:
  
  Storybook here

• tr-tr:
  
  Storybook here

• vi-vn:
  
  Storybook here

• zh-cn:
  
  Storybook here

• zh-tw:
  
  Storybook here

Only 4 components are available to import in canvas app.
For example, Details List is not there.

I suggest that the beta branch is protected with the PR Validation Workflow so that any issues are trapped before they are merged into main. What do you think?
cc @Ramakrishnan24689

After adding a donut chart to the Canvas App screen it shows an "Error loading control" message link. Even though we have done data binding it doesn't function at all. Same error is shown.

Hi guys, do you have any plans to migrate to the latest version of fluent library https://react.fluentui.dev/? There are breaking changes in those library.

Hi,
most of the tests have incorrect data, since there is not enough documentation here for these components, I tried creating the inputs based on the tests. But it is not working as expected. Example of Pivot component. Where the Icons are not rendering.

Items as follows:

Table(
    {
        ItemKey: "item1",
        ItemDisplayName: "Item 1",
        ItemIconName: "Open",
        ItemIconColor: "blue",
        ItemEnabled: true,
        ItemIconOnly: false
    },
    {
        ItemKey: "item2",
        ItemDisplayName: "Item 2",
        ItemIconName: "New",
        ItemIconColor: "blue",
        ItemEnabled: false,
        ItemIconOnly: true
    },
    {
        ItemKey: "item3",
        ItemDisplayName: "Item 3",
        ItemIconName: "Save",
        ItemIconColor: "green",
        ItemEnabled: false,
        ItemIconOnly: true
    },
    {
        ItemKey: "item5",
        ItemDisplayName: "Item 5",
        ItemIconName: "New",
        ItemIconColor: "blue",
        ItemEnabled: false,
        ItemIconOnly: true,
        ItemParentKey: "commandNew"
    },
    {
        ItemKey: "item6",
        ItemDisplayName: "Item 6",
        ItemIconName: "Save",
        ItemIconColor: "green",
        ItemEnabled: false,
        ItemIconOnly: true,
        ItemParentKey: "commandSave"
    },
    {
        ItemKey: "item7",
        ItemDisplayName: "Item 7",
        ItemIconName: "New",
        ItemIconColor: "blue",
        ItemEnabled: false,
        ItemIconOnly: true,
        ItemParentKey: "item1"
    },
    {
        ItemKey: "item8",
        ItemDisplayName: "Item 8",
        ItemIconName: "New",
        ItemIconColor: "blue",
        ItemEnabled: false,
        ItemIconOnly: true,
        ItemParentKey: "item2"
    }
)

based on:

Hi All,

I have been struggling for couple of hours now with creating a simple Detailslist.

I give it a simple SharePoint list dataset with 4 columns (Nazev, Mesto, PSC, Ulice). After adding the dataset, I can see rows appear in the table, but with no column header or data. Following the documentation, next thing I did was I tried to select the fields. When I try to select the fields in the edit fields panel, I can see them there, select them, but when I click Add, it does not add them.

I tried saving the dataset as a local collection using ClearCollect, it did not help. Specifying the columns in the Columns property does not help. To make sure I checked the internal names of the columns in Sharepoint and I am using the right column names in the Columns property. I tried different browsers.

Am I doing something wrong or is this a PowerApps / PowerCat code pomponents bug?

Hi there,

first of all I want to thank the whole team for alle the effort you put into the code components, bridging the gap between fluent ui and the power platform. The outcome is amazing, even if we are just getting started ;)

Our company wants to contribute / extend the existing code components for a project, but getting started developing/contributing is not that easy as using the components, because of the lack of good documentation.

For starters I cloned the repo and tried to get one component (DetailList) up and running. While trying this I'm facing a lot issues like how is the repo intend to be used in form of local development. Starting the test harness results in an empty detail list, trying to use an csv as dataset input is not working and also I were not able to find some mockup data included for development.

After getting in touch with @scottdurow on LinkedIn he kindly asked me to open a request/issue on GitHub.
We would appreciate any help getting started with developing/contributing using this repo. The easiest way would be probably by a teams meeting or chat. It would be nice if someone could contact me there: [email protected]

Thank you guys, and keep up the great work!

For some reason, a local collection that is bound to a Details List doesn't display records in the UI (it is blank), but can be seen in the Power Apps Designer.

The local collection contains rows (confirmed from the Monitor tool).

PowerApps version: 3.24051.23

This was working previously and has only recently happened.

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

Component Version: 1.0.22

I have a DetailsList Component configured as follows:

• Dataverse table as the source, no filters or sorting set in the Items property
• CurrentSortColumn property set to the logical name of the column I want to sort by (Autonumber column)
• CurrentSortDirection set to 'PowerCAT.FluentDetailsList.CurrentSortDirection'.Descending ("1")

This configuration does not sort the list by the set column, it defaults to sorted Ascending by the Primary column on the table.

I've tried specifying a view on the Table that sorts by the desired column, but this doesn't seem to make a difference.

Is this a bug, or have I misunderstood how these properties are supposed to work?

Setting "ItemParentKey" to an Item that has "ItemFarItem=true" does not work - the Child Items are not displayed at all, and the "parent" Item (a FarRightItem) does not display the down chevron to show the fly-out menu.

Either the Documentation needs to be updated to reflect this, or, ideally, the component should be fixed to allow FarRightItems to have children.

Currently, the build number is incremented with each release in line with the recommended PCF deployment practices.
The solution is version stamped with the same version as the PCFs.

To make it easier for forks to build/test new versions, what do you think about moving the release increment to the minor version instead? This will make it easier for branches/forks to deploy/test new versions without preventing future import version collisions due to the local version being higher than the new release version.

E.g.

1. Released version -> 1.8.0
2. Forked/branch version deployed to test environment ->1.8.1 -> 1.8.2 etc.
3. New version released ->1.9.0
4. Forked/branch version deployed to test environment ->1.9.1 -> 1.9.2 etc.
5. And so on....

This would need a change to the release workflow, moving the incrementing version to the minor variable, rather than the build version.

Thoughts?