Open RainCityAndrew opened 2 months ago
Thanks for reporting! I will look into this and get back to you.
Hello, just to add that I experienced this today! I was very confused, as I had no reason to believe that the new editor wouldn't work.
I have used the old form editor for this control. Which is not a problem of course, but worth flagging with you, Khoa. Cheers
@wenstarner thanks for your input! it looks strange! could be a bug in the modern form editor. It doesn't happen for me though. can you try removing the field from the form > save and publish > close the form > open the form and add the field > add Lookdown component again? @RainCityAndrew @wenstarner just to check if the problem is fixed by MS already and we can refresh the field metadata by removing and adding it back.
Hi, I followed your steps and it's not working again. So strange!
Yesterday, I tried many times without luck (in the new form editor). To confirm, this time just now, I've followed your instructions exactly, and closed the tab with the modern form editor, and opened a new tab to load it up again. Please let me know if there's anything else I can do to help.
Sorry to double-post, but a small update:
I thought this was a glitch, so removed and then re-added the component in the classic editor. And now the group labels continue to display in black... not a problem, but another thing I thought useful to point out.
EDIT: I updated a few further settings (without removing the component), and the group labels are blue again:
thanks @wenstarner! so there must be differences in metadata between the two editors 🤔. I'll create a new environment and try it again.
I'll add that I tested all the ways mentioned here and have the same results of getting it to work by changing or applying a setting in the old editor. I'm using Firefox if that might make a difference.
Also a side note, it's not possible to completely null the option once one is entered
Ok I'm able to replicate it. it's obviously because of the modern editor. there are missing metadata, which are needed within the control such as Default View Id, when a lookup field is added in the modern editor. see images below
Lookup field when added in Classic Editor
Lookup field when added in Modern Editor
we can use classic editor to add the field, but one problem is when we open the form in modern editor, the control label is missing. the form is still working fine for end users but it doesn't look right in the modern editor.
now I found a workaround for the missing metadata. in modern editor:
I think there's not much I can do to fix this. I'll add this as a known issue in wiki and keep this issue open so we can monitor when it is resolved by MS.
cc @RainCityAndrew @wenstarner
Amazing and nice find for the workaround! I hate using the old editor so this is perfect.
Thank you so much for the beyond amazing work on your components they're one of the best!
I agree with @RainCityAndrew, thank you @khoait for all your time and effort! This is so much appreciated :) The workaround is great, and the detail is super interesting to read about!
Component
Lookdown v1.2.0
Describe the bug
Control doesn't work when added to field using new power apps form editor.
Steps to Reproduce
Steps to reproduce the behavior:
Expected behavior
To be addable from the new form editor since the old editor is mostly deprecated and difficult to use
Actual behavior
A clear and concise description of what you experienced.
Screenshots
This is how the control looks after saving it in the old school editor. Label is invisible but it works on the record as shown below.
Additional context
I switched to a different PCF control with similar functionality and this was noted as a bug which brought me back to test if it's the same case here https://github.com/drivardxrm/LookupDropdown.PCF/issues/29