ashlega / itaintboring.pcfcontrols Goto Github PK

At the footer of the dropdown would it be possible to show a + new button to quick create the record and associate it?

Has anybody tried this control in the Dynamics Outlook App? It renders correctly but it fails to save/edit/delete records in the N:N.

Is there an option to "Select All" much like a multi-select option set? Use case is I have States as custom entity and a user needs to select all states to do business in, they would have to select each one individually but would prefer to select all. Thanks!

Hi Alex

When I try to import the demo solution I get the following message about missing dependencies.

I have tried all the options, but not sure where the mistake is, any help would be greatly apprecated.

Thank you

These values are depicted in my view:
NTONDATA:{"actions":[{"associate":true,"guid":"378e9aed-e122-ed11-b83d-000d3ab32811"},{"associate":true,"guid":"9be4c7f6-e122-ed11-b83d-000d3a65303f"}],"len":"hdm_sma_std_lehrgang","ida":"hdm_sma_std_lehrgangid","na":"hdm_sma_std_lehrgangsname","re":"hdm_techniker_hdm_sma_std_lehrgang","rn":"hdm_Techniker_hdm_sma_std_Lehrgang"}

This is how the lookup looks like in the form:

Any help is much appreciated, I also can provide more information if needed/ desired.

It seems like the reference in a N:N Multiselect are not saved when creating a new record. Any chanse you can fix this?

Hi,

In N:N control, Passing FetchXML is not working.
I want to add custom field sorting in the control to display the records in order.
Either need to add sorting attribute on the N:N control or fetchxml should support this feature.

Hi,
I am trying to use the NToN control on a Quick Create form for a new record. The drop-down of the records is working. But on selecting a record from the drop-down i get the following error "Entity Reference cannot have Id and Key Attributes empty." It does select the record, but it doesn't save it the relationship.

Thank You!

Origen Entity: opportunity (Engagement)
Destination Entity: pes_sector (Sector)

I config a N:N relationship and it gives me below error:

My entity relationship config:

and the filed names are correctly written in the control:

May the control has any error?

It would be beneficial if the value for "FetchXml Web Resource" must not be the absolute path to the web ressource.

Instead of :
https://myorg.crm4.dynamics.com/WebResources/new_fetchxml

this should be enough:
new_fetchxml

because the first part of the path could be created dynamically. Therefore no extra configuration is needed when deploying a solution to another CRM organization.

As far as I see, this line of code should be adjusted:

hi,

i want to know if there is a way to refresh the NtoN pcf within the js file or any other file within the same form?

Or did I configure it wrong

I have tried to use this PCF, but once save and after coming back to same Record the value doesn't appear on the text box. While in database value do appear. So can you please help me in resolving this.

Hi @ashlega Thanks for the providing the cool multiselelct lookup PCF control.

I imported the solution (unmanaged) and configured it as below. But it is throwing me an error as below.

The Error is as below

Were you able to replicate the Issue

Great set of controls here.

However, when using a web resource containing FetchXml to load the data, this does not work in the mobile app. This would be due to the XMLHttpRequest object being used to retrieve the web resource.

Suggest using WebAPI.retrieveMultipleRecords against the webresource endpoint to retrieve the content instead. If using a resx web resource this will be presented as name value pairs in a JSON string from the contentjson attribute.

I installed the solution ItAintBoringPCFControls.zip, then placed in a form and configured as indicated. The control does display all the records in the related entity but after making a selection, it displays the error mentioned on the title "The URI segment '$ref' is invalid after the segment ..."

Has anybody run into this?

Hi,
I have recently downloaded and installed these controls and am trying to use the tree control on the out of box relationship between knowledgearticle and category. I believe I have configured everything correctly (shown below) however I simply get a message box with [Object Object] and the control doesn't render. I have done a little further digging and it seems like it is getting a 404 for the many to many entity query because, whilst it is passed into the Xrm.WebApi call as all lower case, it somehow is changed to title case before executing the request, resulting in 404. To me, this seems to be a UCI bug with Xrm.WebApi as doing the same call outside of the PCF has the same outcome. Being on Knowledge Article, the classic interface does not support PCF so I can't validate if this worked otherwise.

Instance is 2020 with wave 2 enabled - v1710 (9.1.0.26143 online)

Has anyone else experienced this/logged with Microsoft?

Settings are:
Table Grid: All Categories
Tree Entity Name: category
Tree Entity Lookup Attribute: parentcategoryid
Tree Entity Name Attribute: title
Relationship Name: knowledgearticle_category
Relationship Entity: knowledgearticlescategories

Hi guys,

I am trying to import the demo solution to my environment. But it shows an error message for the security role and pcf control. Any idea how to solve this? I want to know how to use the N to N multi-select. thanks before!

Hi Alex,

First of all - great component you have made here! It solves a lot of issues by either using a multi-select field (searching) or out-of-the-box sub-grid (user experience).

I read your blog post about the control. Here you mention, that using the hierarchy, it is possible to find all records “under” one of the parent tags.

From a search perspective (and here I am also thinking about canvas apps), I was wondering if it would make sense, to automatically create a many-to-many relationship for the parent record(s) as well when a child is selected.

E.g. in your example, when Paragraph 1.1. is selected both Paragraph 1.1. and Section 1 would be created as many-to-many records:

When searching, e.g. using Advanced Find, you can then just rely on the Primary Key (Tag in your example) field and use the equal operator. E.g. if you make query where Tag equals Section 1 then I will also find the records, where Paragraph 1.1 and Paragraph 1.2 are selected.

And if you have a deeper nested hierarchy, you will not have to worry about using the Parent tag field and which operators to use, e.g. under or eq-or-under. Moreover, you can add a sub-grid on the form of the Tag entity, to show related records, when there is a direct relationship between the two records.

Best regards,
Niels

Hi,

For the NtoNMultiSelect Control, would it possible to select a option multiple times?
My requirement is that i should be able to add the same option again if necessary.

Thank You!