carfup / pcfcontrols Goto Github PK

Hi,

Getting an issue when saving decimals using the quick edit form.
I have installed the latest version PCF Controls 1.3.2.1
We had raised a similar issue before ( #20) but it does not seem to be fixed.
Could you please help?

An error occurred during the update.

An error occurred while validating input parameters: Microsoft.OData.ODataException: Cannot convert a value to target type 'Edm.Decimal' because of conflict between input format string/number and parameter 'IEEE754Compatible' false/true.
at Microsoft.OData.JsonLight.ODataJsonLightPropertyAndValueDeserializer.ReadPrimitiveValue(Boolean insideJsonObjectValue, IEdmPrimitiveTypeReference expectedValueTypeReference, Boolean validateNullValue, String propertyName)
at Microsoft.OData.JsonLight.ODataJsonLightPropertyAndValueDeserializer.ReadNonEntityValueImplementation(String payloadTypeName, IEdmTypeReference expectedTypeReference, PropertyAndAnnotationCollector propertyAndAnnotationCollector, CollectionWithoutExpectedTypeValidator collectionValidator, Boolean validateNullValue, Boolean isTopLevelPropertyValue, Boolean insideResourceValue, String propertyName, Nullable1 isDynamicProperty) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadEntryDataProperty(IODataJsonLightReaderResourceState resourceState, IEdmProperty edmProperty, String propertyTypeName) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadPropertyWithValue(IODataJsonLightReaderResourceState resourceState, String propertyName, Boolean isDeltaResourceSet) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.<>c__DisplayClass9_0.<ReadResourceContent>b__0(PropertyParsingResult propertyParsingResult, String propertyName) at Microsoft.OData.JsonLight.ODataJsonLightDeserializer.ProcessProperty(PropertyAndAnnotationCollector propertyAndAnnotationCollector, Func2 readPropertyAnnotationValue, Action2 handleProperty) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadResourceContent(IODataJsonLightReaderResourceState resourceState) at Microsoft.OData.JsonLight.ODataJsonLightReader.StartReadingResource() at Microsoft.OData.JsonLight.ODataJsonLightReader.ReadResourceSetItemStart(PropertyAndAnnotationCollector propertyAndAnnotationCollector, SelectedPropertiesNode selectedProperties) at Microsoft.OData.JsonLight.ODataJsonLightReader.ReadAtStartImplementationSynchronously(PropertyAndAnnotationCollector propertyAndAnnotationCollector) at Microsoft.OData.ODataReaderCore.ReadImplementation() at Microsoft.OData.ODataReaderCore.InterceptException[T](Func1 action)
at System.Web.OData.Formatter.Deserialization.ODataReaderExtensions.ReadResourceOrResourceSet(ODataReader reader)
at System.Web.OData.Formatter.Deserialization.ODataResourceDeserializer.Read(ODataMessageReader messageReader, Type type, ODataDeserializerContext readContext)
at System.Web.OData.Formatter.ODataMediaTypeFormatter.ReadFromStream(Type type, Stream readStream, HttpContent content, IFormatterLogger formatterLogger)

Thanks

Would it even be possible to call a Javascript function on successfull save?

My idea is that your form is smart for updating data in lookup entity. When the entity is updated, the current form might need a refresh or something like that. In this case we could call our own Javascript function. The function name could be inserted where we setup the pcf with lookup name etc.

Not even sure if possible:)

Nice Work!!!! I have a small question relating to date field. Its displaying date with a day difference. Do you know whats causing this issue and Do you have a workaround for this issue??
Your control was really helpful..

Hi
This is great control which is helping my team.

Will be more happy if we get this fixed as well.

Field names are not displaying "Display" name from the form, it is getting name from the Entity field name
We have different display names in different forms, this is confusing users from actual form a and quick edit form
Attached the image which explains more.
It will be great with this change.

It would be nice to be able to use your control even for quick create purposes incase there is no record related.

Will it be possible to support the Customer Lookup on Contact? parentcustomerid I believe it is called:)

Hi Clement,

Thanks for your prompt reply in discussion.

Regarding to the issue, we had installed the solution that last modified on 24 Jul and encountered below error when saving value to user lookup field. We have couple of user lookup fields in the quick edit form and all meet the same error.
The lookup relationship is between a new custom entity and user entity.

Besides, I found a post that may be related to the error. Thanks.
https://yaweriqbal.com/2019/10/28/web-api-an-error-occurred-while-validating-input-parameters/

"An error occurred during the update.

An error occurred while validating input parameters: Microsoft.OData.ODataException: An undeclared property '{field name}' which only has property annotations in the payload but no property value was found in the payload. In OData, only declared navigation properties and declared named streams can be represented as properties without values.
at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadUndeclaredProperty(IODataJsonLightReaderResourceState resourceState, String propertyName, Boolean propertyWithValue)
at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadPropertyWithoutValue(IODataJsonLightReaderResourceState resourceState, String propertyName)
at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.<>c__DisplayClass9_0.b__0(PropertyParsingResult propertyParsingResult, String propertyName)
at Microsoft.OData.JsonLight.ODataJsonLightDeserializer.ProcessProperty(PropertyAndAnnotationCollector propertyAndAnnotationCollector, Func2 readPropertyAnnotationValue, Action2 handleProperty)
at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadResourceContent(IODataJsonLightReaderResourceState resourceState)
at Microsoft.OData.JsonLight.ODataJsonLightReader.StartReadingResource()
at Microsoft.OData.JsonLight.ODataJsonLightReader.ReadResourceSetItemStart(PropertyAndAnnotationCollector propertyAndAnnotationCollector, SelectedPropertiesNode selectedProperties)
at Microsoft.OData.JsonLight.ODataJsonLightReader.ReadAtStartImplementationSynchronously(PropertyAndAnnotationCollector propertyAndAnnotationCollector)
at Microsoft.OData.ODataReaderCore.ReadImplementation()
at Microsoft.OData.ODataReaderCore.InterceptException[T](Func`1 action)
at System.Web.OData.Formatter.Deserialization.ODataReaderExtensions.ReadResourceOrResourceSet(ODataReader reader)
at System.Web.OData.Formatter.Deserialization.ODataResourceDeserializer.Read(ODataMessageReader messageReader, Type type, ODataDeserializerContext readContext)
at System.Web.OData.Formatter.ODataMediaTypeFormatter.ReadFromStream(Type type, Stream readStream, HttpContent content, IFormatterLogger formatterLogger)"

Going through the issues here I haven't seen one like this:

The quickedit works but it never stops loading. It also removes the fields if I press refresh and same loading graphic.

It does look like this is flagging in the console:

My textfield with the control settings

any top of the head ideas?

I do not have any js or business process flows attached to the lookup field.

We are on version 1.4.0.0 of the Carfup_PCFControls. It is a great tool, but we have run into an issue with using it.

We have included system required fields in our Any Composite setup and they are not being enforced on save (see the steps below for details of our setup and testing).

When we saw that the composite field wasn't enforcing the required fields we thought perhaps the composite field itself had to be set to required. However, that did not resolve our issue either. Because not all the fields are included in the composite are required, if just one of the optional fields is populated, the record will save and will not enforce the system requirement of the other fields in the composite.

Steps to duplicate our issue:

1. On Contact entity, set the OTB field First Name to Required
2. On Contact entity, set the OTB field Last Name to Optional
3. On Contact entity, create customer single line text field called Full Name
4. Add the 3 above fields to a Contact Form
5. Add the Any Composite Control to the customer Full Name field
6. Configure Any Composite Control by adding Field 1 = First Name and Field 2 = Last Name
7. Save and Publish the above updates
8. Create a New Contact Record
9. Click on the custom Full Name field
10. Populate only the Last Name field in the composite control
11. Click Done to exit the composite control
12. Save the contact record
    • Expected Result: Error message advises user that First Name field is required and prevent save
    • Actual Result: Field requirement for First Name is not enforced, contact record is saved

Hello Clement,
When I create a record using Flow and then open the record, the control doesn't loads at the first time I open it but if i close and then open again then it loads properly,
here is a print screen it stays like that:

then when i go out from the form and reopen it, it loads:

I'm getting this error > An error occurred undefined.

Added the control on std fax field, trying to show the 'account contact card' via the primary contact lookup field in the Account form.

Configuration:

I'm I doing something wrong??

Hi,

After installing your managed PCF : Quick Edit Form solution, and adding a lookup field onto a form - I cannot see the PCF : Quick Edit Form Control to add as a Control to the new look up field.

Any thoughts why this could be the case? and is anyone potentially experiencing this issue after enabling the Recent 2021 release.

Thanks,

Hi Clement,

We recently tried using the Lookup field within the Quick Edit Control and came across an error.
For reference:

• we have the quick edit control on a text field on the opportunity
• we have a quick view form with only a lookup field on it (ktl_atshris)

Error message when updating the field and saving in the quick edit:

An error occurred while validating input parameters: Microsoft.OData.ODataException: An undeclared property 'ktl_atshris' which only has property annotations in the payload but no property value was found in the payload. In OData, only declared navigation properties and declared named streams can be represented as properties without values. at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadUndeclaredProperty(IODataJsonLightReaderResourceState resourceState, String propertyName, Boolean propertyWithValue) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadPropertyWithoutValue(IODataJsonLightReaderResourceState resourceState, String propertyName) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.<>c__DisplayClass9_0.b__0(PropertyParsingResult propertyParsingResult, String propertyName) at Microsoft.OData.JsonLight.ODataJsonLightDeserializer.ProcessProperty(PropertyAndAnnotationCollector propertyAndAnnotationCollector, Func2 readPropertyAnnotationValue, Action2 handleProperty) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadResourceContent(IODataJsonLightReaderResourceState resourceState) at Microsoft.OData.JsonLight.ODataJsonLightReader.StartReadingResource() at Microsoft.OData.JsonLight.ODataJsonLightReader.ReadResourceSetItemStart(PropertyAndAnnotationCollector propertyAndAnnotationCollector, SelectedPropertiesNode selectedProperties) at Microsoft.OData.JsonLight.ODataJsonLightReader.ReadAtStartImplementationSynchronously(PropertyAndAnnotationCollector propertyAndAnnotationCollector) at Microsoft.OData.ODataReaderCore.ReadImplementation() at Microsoft.OData.ODataReaderCore.InterceptException[T](Func`1 action) at System.Web.OData.Formatter.Deserialization.ODataReaderExtensions.ReadResourceOrResourceSet(ODataReader reader) at System.Web.OData.Formatter.Deserialization.ODataResourceDeserializer.Read(ODataMessageReader messageReader, Type type, ODataDeserializerContext readContext) at System.Web.OData.Formatter.ODataMediaTypeFormatter.ReadFromStream(Type type, Stream readStream, HttpContent content, IFormatterLogger formatterLogger)

Please let me know how I can help.

Hi,
Having an issue where the I am getting the message "Could not find a property named 'undefined' on type 'Microsoft.Dynamics.CRM.documententityname" when I try to create a new record on a form with the File upload control present.

My setup:

• File control is on parent entity (crca7_equipmentrental(s))
• File data field is on related entity (crca7_equipmentdocuments)
• This only happens if I go directly from the main crca7_equipmentrentals grid and click new. If I create an equipment rental from a different sub grid it appears to work.
  

Would you be available for any custom support? This control is incredibly useful for our specific use case and it'd be great if we could get it working.

Thanks,
Dylan

Hello,
I noticed that users receive an unspecific error message ('An error occurred: [object Object]') when trying to use the Quick Edit Form to view data from an entity they do not have access to. Is it possible to hide it or give them more meaningful information within it?

This looks awesome! Would you consider adding support for a pop out version that uses the fabric UI panel? This way it would open like the current quick create form does.
Office Fluent UI

In your comment on your page, I'm not sure what you mean by a PCF that will somehow become empty.

Do you feel this PCF will be superseded by the new Xrm.Navigation.nagivateTo functionality?

If we make the field read-only and then unlock it, we can no longer type in the field (the screen must be refreshed to be able to access the field again)
Carfup version 1.3.3.2

Hi, I'm very impressed with the PCF Quick Edit control.
Are there any options for a more commercial friendly license such as MIT?

Do you mind changing the license?

Best regards.

When importing, it doesn't show any names in the Custom Controls section of the solution (managed). Would look a little better if they had names:)

Hi, thank you for this awesome control!

I really have no idea if it's possible, but I thought of adding subgrids to have the ability to create related records to an account for example.

In the use case I'm thinking about, I have an appointment regarding an account and I can see the related annual budgets (custom entity) of the account on the appointment form and I would be able to create a new annual budget record for 2020.

I tried to add it in the actual control, I can't see the subgrid and the loading control doesn't seem to stop.

Don't know if my suggestion is relevant, but thanks again for the control!

If a quick view form is designed on multi columns, being able to render this on the control too.

It would be great if we can display the data on the Quick Edit Form from a grandparent entity and not only Parent.

We have a scenario where a grandparent entity, parent entity and transactional child entity are present. On the child entity, we would like to show the grandparent data in the PCF control.

I have activated the duplicate rule detection but from the edit quick view control it doesn't detect duplicated records. It would be great if this feature is aggregated to this control. Thank you very much!

Quick Edit Form is great and it provides two key benefits over an OOB Quick View Form, they are:

• Multi Column Layout
• Multi line fields

It would be great for this control to render as read only also. It can be used as an enhanced Quick View form also.

Embrace required fields

Hi, i have a few that i was hoping could get answered. If this is not the appropriate place to put them then please notify me so that i can move them.

• Is it possible to add custom behaviour to the PCFControls i.e. to extend or edit current behaviour that better suits our needs ?

• We noticed that the translation in some languages are a little "off" for the refresh / update button, is there any way to customize those buttons or translations ?

Hello Clément,

We've implemented the PCF control and it's performing well. However, we've encountered an issue with it when using the mobile version. The PCF control is applied on a Quick Create form.

Whenever we select one of the controls, it shuts down immediately. Do you happen to know if there's a fix for this?

Best regards,

Tex

Hi,

we discovered this PCF Control on pcf gallery and i must say it is truly amazing. cuts out so much custom development that is required to accomplish what you did. so thanks.

but i did notice 2 small issues from my end, if i change the label of one of the fields on the quick view form, the custom control uses the default label of the given field.
the second issue i noticed; we have a requirement where we want to use this control twice on the same form but load different quick view forms for each instance. i followed the documentation and entered different form ids for the separate instances but the same form shows by both areas.

Once again, thanks.
Leibish Ringel

Hi, first of all this is a great control and has been a joy to put into use.

Second I've noticed an issue on the QView Form control and that is that moderately long labels tend to be buried under the inputs or rather the inputs tend to take most of the space one assigns to them

Thanks for listening!

What is used as separator?
Regards,
Diego.

I tried adding 1044 Norwegian as a file in string library, but never actually used GitHub directly. Therefore I am not sure I have done it correctly:)

Hello,
I am new to Dynamics and PCF controls, i tried to integrate the control and passed the parameters as suggested by you, but i am facing an issue. Instead of loading the form, it gives an option to create a new opportunity.

I have created a new quick view in the Opportunity entity and passing its GUID in the guid paramter. i could not find a way to get the Guid from anyother source, i got it from the URL of the form.

this is the form i have created for this purpose.

and here is the configuration of the control,|

Could you please have a look and let me know what possible mistake i am making here?

Thanks in advance.

Hi Clement,

This PCF (quick edit form) is really great and really helps improve user experience, so thanks very much.

Just a question around the multiline text fields: when entering the data, the text area automatically expands, so if I input 15 lines of text, the box shows all 15 lines at once. However, when I refresh the main record or navigate away and come back, it goes back to 3.5 x line height and there is no scroll bar on the text area either, so it's hard to view more than the 3 lines of text at once. Is it possible to have the text areas of these multiline text fields always expand to match the length of the content? So if I'm coming back to view my 15 lines of text I can see all 15 lines of text at once?

I am using the Quick Edit Form to look up to the Contact record. One of the fields that we are showing is the OOB "birthdate" field (Date Only). When viewing the Contact record the date displays as desired e.g. 4/22/1972 however when viewed through the Quick Edit Form it shows 4/21/1972, a day earlier.
Even if you enter the date in via the Quick Edit Form it will update the Contact record appropriately but will still reflect incorrect in the Quick Edit Form. DateTime fields do not appear to be affected.

PCF: Carfup.SiretValidator (version 1.3.0.0)
Dynamics version (crm4): Version du serveur: 9.1.0000.18350 (Wave 1), Version du client: 1.4.830-2005.3
Test on 4 different environment (also 3 different users).

Hello Olivier,
After filling in the Siret field with a valid number, when I save the record the field is filled in the db.
If I open the record the field is empty in the form (but the field is filled in the db).
Of course if I save the record again then the field is cleared.
For an existing record with a valid Siret number, if I open it the field is empty in the form. If I save the record then the field is emptied.
I think it occurs since Wave 1 have been deployed.

Many thanks !

Hi Clement, first of all- I am a big fan and am greatly appreciative of your open source contributions.

I want to give you a heads up that this control corrupts the Base64 encoding on the file type, but I have to admit I have no idea how. All I know is that I can upload and download XLSX just fine through your control, but if I try to download an XLSX file using the SDK that I uploaded with your control, it is corrupted. I can upload with the default file control just fine and access with the SDK with no issues. I'm guessing something funny is happening in the upload process that encodes the metadata differently than the SDK expects, but haven't dug in that deeply.

Thanks again,

Joe

The field doesn't seem to refresh on the form when updating the value with xrm's .setValue function.
Value is well filled, it can be retrieved with .getValue function afterward but the value edit doesn't show. Only after reloading the form does it show the updated value.

Hello Clement, me again with a new request. Add the posibility to block a field (read only.).., the requirment is that I have a field that first is empty but the when the user complete the field and saves it i want to block it. And another thing is to make some fields required...

Thanks!!!

Hi,

This is in regards to the Quick Edit Form.
I have a lookup field on the edit form and when a user select the field to add/edit the value they receive a form with just the lookup field and i cannot figure out how to custom filter the lookup view.
Can you help?

Thank You!
Leibish Ringel

Thanks for this control this really saved our development time. I am facing one issue with the date field, will be thankful if someone help me to resolve this issue.
Date of birth field is optional in my contact form and this control is displaying "1/01/1970" it should be null as per the record data.
How can I set this value to null. This is misleading the users unable to differentiate its between actual value and this default value.

Hi Clément,

I hope you are going well. C'est Dimitri :)

I have been using this PCF with many customers and never had any issue.
On my current project, we found out that:

• when we want to update a "date only" field we have the following error:

Error identified in Payload provided by the user for Entity :'', InnerException : Microsoft.OData.ODataException: Cannot convert the literal '2023-04-19T08:40:36.076Z' to the expected type 'Edm.Date'. ---> System.FormatException: String '2023-04-19T08:40:36.076Z' was not recognized as a valid Edm.Date.

at Microsoft.OData.PlatformHelper.ConvertStringToDate(String text)
at Microsoft.OData.ODataPayloadValueConverter.ConvertStringValue(String stringValue, Type targetType)
at Microsoft.OData.ODataPayloadValueConverter.ConvertFromPayloadValue(Object value, IEdmTypeReference edmTypeReference)
--- End of inner exception stack trace ---
at Microsoft.OData.ODataPayloadValueConverter.ConvertFromPayloadValue(Object value, IEdmTypeReference edmTypeReference)
at Microsoft.Crm.Extensibility.ODataV4.CrmPrimitivePayloadValueConverter.ConvertFromPayloadValue(Object value, IEdmTypeReference edmTypeReference)
at Microsoft.OData.JsonLight.ODataJsonLightReaderUtils.ConvertValue(Object value, IEdmPrimitiveTypeReference primitiveTypeReference, ODataMessageReaderSettings messageReaderSettings, Boolean validateNullValue, String propertyName, ODataPayloadValueConverter converter)
at Microsoft.OData.JsonLight.ODataJsonLightPropertyAndValueDeserializer.ReadPrimitiveValue(Boolean insideJsonObjectValue, IEdmPrimitiveTypeReference expectedValueTypeReference, Boolean validateNullValue, String propertyName)
at Microsoft.OData.JsonLight.ODataJsonLightPropertyAndValueDeserializer.ReadNonEntityValueImplementation(String payloadTypeName, IEdmTypeReference expectedTypeReference, PropertyAndAnnotationCollector propertyAndAnnotationCollector, CollectionWithoutExpectedTypeValidator collectionValidator, Boolean validateNullValue, Boolean isTopLevelPropertyValue, Boolean insideResourceValue, String propertyName, Nullable1 isDynamicProperty) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadEntryDataProperty(IODataJsonLightReaderResourceState resourceState, IEdmProperty edmProperty, String propertyTypeName) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadPropertyWithValue(IODataJsonLightReaderResourceState resourceState, String propertyName, Boolean isDeltaResourceSet) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.<>c__DisplayClass9_0.<ReadResourceContent>b__0(PropertyParsingResult propertyParsingResult, String propertyName) at Microsoft.OData.JsonLight.ODataJsonLightDeserializer.ProcessProperty(PropertyAndAnnotationCollector propertyAndAnnotationCollector, Func2 readPropertyAnnotationValue, Action2 handleProperty) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadResourceContent(IODataJsonLightReaderResourceState resourceState) at Microsoft.OData.JsonLight.ODataJsonLightReader.StartReadingResource() at Microsoft.OData.JsonLight.ODataJsonLightReader.ReadResourceSetItemStart(PropertyAndAnnotationCollector propertyAndAnnotationCollector, SelectedPropertiesNode selectedProperties) at Microsoft.OData.JsonLight.ODataJsonLightReader.ReadAtStartImplementationSynchronously(PropertyAndAnnotationCollector propertyAndAnnotationCollector) at Microsoft.OData.ODataReaderCore.ReadImplementation() at Microsoft.OData.ODataReaderCore.InterceptException[T](Func1 action)
at System.Web.OData.Formatter.Deserialization.ODataReaderExtensions.ReadResourceOrResourceSet(ODataReader reader)
at System.Web.OData.Formatter.Deserialization.ODataResourceDeserializer.Read(ODataMessageReader messageReader, Type type, ODataDeserializerContext readContext)
at System.Web.OData.Formatter.ODataMediaTypeFormatter.ReadFromStream(Type type, Stream readStream, HttpContent content, IFormatterLogger formatterLogger).

• For date time fields it works like a charm

I also tested in this a trial environment and do have the same issue.

Attached you will find a gif that hopefully it will be more clear to you.
Do you anything that could cause this?

In case you need to contact me, I am at your diposal (linkedin, here) etc...

Any reason these fail? Would have thought they would work since Money is supported?

An error occurred during the update.

An error occurred while validating input parameters: Microsoft.OData.ODataException: Cannot convert a value to target type 'Edm.Decimal' because of conflict between input format string/number and parameter 'IEEE754Compatible' false/true.
at Microsoft.OData.JsonLight.ODataJsonLightPropertyAndValueDeserializer.ReadPrimitiveValue(Boolean insideJsonObjectValue, IEdmPrimitiveTypeReference expectedValueTypeReference, Boolean validateNullValue, String propertyName)
at Microsoft.OData.JsonLight.ODataJsonLightPropertyAndValueDeserializer.ReadNonEntityValueImplementation(String payloadTypeName, IEdmTypeReference expectedTypeReference, PropertyAndAnnotationCollector propertyAndAnnotationCollector, CollectionWithoutExpectedTypeValidator collectionValidator, Boolean validateNullValue, Boolean isTopLevelPropertyValue, Boolean insideResourceValue, String propertyName, Nullable1 isDynamicProperty) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadEntryDataProperty(IODataJsonLightReaderResourceState resourceState, IEdmProperty edmProperty, String propertyTypeName) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadPropertyWithValue(IODataJsonLightReaderResourceState resourceState, String propertyName, Boolean isDeltaResourceSet) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.<>c__DisplayClass9_0.<ReadResourceContent>b__0(PropertyParsingResult propertyParsingResult, String propertyName) at Microsoft.OData.JsonLight.ODataJsonLightDeserializer.ProcessProperty(PropertyAndAnnotationCollector propertyAndAnnotationCollector, Func2 readPropertyAnnotationValue, Action2 handleProperty) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadResourceContent(IODataJsonLightReaderResourceState resourceState) at Microsoft.OData.JsonLight.ODataJsonLightReader.StartReadingResource() at Microsoft.OData.JsonLight.ODataJsonLightReader.ReadResourceSetItemStart(PropertyAndAnnotationCollector propertyAndAnnotationCollector, SelectedPropertiesNode selectedProperties) at Microsoft.OData.JsonLight.ODataJsonLightReader.ReadAtStartImplementationSynchronously(PropertyAndAnnotationCollector propertyAndAnnotationCollector) at Microsoft.OData.ODataReaderCore.ReadImplementation() at Microsoft.OData.ODataReaderCore.InterceptException[T](Func1 action)
at System.Web.OData.Formatter.Deserialization.ODataReaderExtensions.ReadResourceOrResourceSet(ODataReader reader)
at System.Web.OData.Formatter.Deserialization.ODataResourceDeserializer.Read(ODataMessageReader messageReader, Type type, ODataDeserializerContext readContext)
at System.Web.OData.Formatter.ODataMediaTypeFormatter.ReadFromStream(Type type, Stream readStream, HttpContent content, IFormatterLogger formatterLogger)

Feedbacks from Marc El Khoury

1. I had the status reason field on the form that got displayed and instead of being an optionset, the field contained the value which was editable as a text field.
2. That same form contained an optionset field but with a local optionset and it worked fine.
3. The second form which never got displayed contained only two optionset fields but they were global. So I think this is the reason why the component isn't loading the form: it can't read global optionsets.
4. Would it be possible to not display the quick form's section label if it's configured to be hidden? The idea behind this request is to display the component as seamlessly as possible so that users don't even know that they are modifying another record.

The composite field control is great in that it brings back a much needed feature to manage space. One of the biggest culprits requiring this are addresses. Presently the composite control allows you to enter a separator such as a comma or space.

It would be nice if it would be possible to add newline as a character to format the address in multiple lines.

One up from that would be to specify a specific format using fields in the composite and separators such as:
address1_street1CRLFaddress1_street2CRLFaddress1_city,%20address1_stateorprovince%20address1_postalcode

which would return:
address1_street1
address1_street2
address1_city, address1_stateorprovince address1_postalcode

It would be great if the composite anything could be bound to either a multi lines of text or single line of text object on the form.

Hi Clement,

I am working as part of the development team in my current company and we found out the QuickEditForm PCF custom control and it is amazing!

I downloaded the source code for the branch where it has the 1.3.2.1 tag, and I imported in my sandbox instance for a proof of concept. I found out the QuickEditForm is showing fields where they are configured for not being visible by default, and I proceeded to modify the source code in order to not show in the PCF custom control fields that are marked as not visible by default.

Due to this PCF control is under Open Source, we would like to know if there is anything else that you would require from us for using your control in addition to commit the change that I implemented. The development team is planning to use this control internally in the company for a few projects with no intention to redistribute to anyone else.

Regards,
Aldo Garcia

Goal : Have a clickable composite field (phone number + extension with separator) with the OOB function (opening task + the Android/iOS phone App or potentially the VoIP system in place)

The separator is important, In order to dial the phone number first and then the extension because Android and iOS does not react the same.

Android accepts both "," (directly) or ";" (need manual validation)
iOS only accepts ","