-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List Formatting - Issue using inline edit and setValue in "customCardProps" #9614
Comments
@aaclage we are currently looking into this. |
Dear @shagra-ms @arkogupta, Thank you for the update, here my feedback on current status: 1- inlineEditField was fixed Hope second point can also be fixed, again thank you for your support. |
Dear Mr. @tpodugu-ms, @shagra-ms, @arkogupta, Report issue Tested capability to update on modal dialog based on sample and is working now. I will close ticket. Thank you for your support, |
Dear @tpodugu-ms, @shagra-ms, @arkogupta, I use the following base as described here and issue returns, looks like a roolback or something. |
Dear @tpodugu-ms, @shagra-ms, @arkogupta, Can you validate this issue also return from your side? |
Hi @aaclage, Thanks for following up. I will check this and update. |
Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
Declarative list formatting
Developer environment
None
What browser(s) / client(s) have you tested
Additional environment details
Browser
Describe the bug / error
Dear Mr. @shagra-ms,
I would like to report the following issue and inconsistent behavior when using some actions in List View but not when using WebPart List in SharePoint Page:
Steps to reproduce
4- Create SharePoint Page
5- Add WebPart List with new View
6- Test options on support gif
Expected behavior
The gif below provide current behavior when List is View mode and List is included in SharePoint Page but behavior is not the same as shown in image bellow.
It's expected that same functionalities should be able to work on both sides.
The text was updated successfully, but these errors were encountered: