Size increase of .sppkg packages with heft/v1.22
After upgrading our solution to SPFx 1.22.rc-0 and switching to the new heft build toolchain our .sppkg packages have suddenly grown massively in size. They are more than double the size of the 1.21 version. Is there a reason for this? Is there anything we can do to reduce the package size back to what it was previously? Our main solution contains both web parts and list extensions, split into several bundles. Let me know what other details would be helpful.
Is Creating Multiple ClientContext Instances Efficient in CSOM for one Site Url?
Is it efficient to create a new ClientContext for each site URL and for each query, such as getting site users, lists, groups, and group members from the Web object? These queries can return a very large number of items, and CSOM does not support paging when retrieving data from Web properties. Because of this, there is a risk of memory issues. In this case, is creating multiple ClientContext objects a good approach? Also, how does ClientContext work internally, and how does it handle memory and performance?
SharePoint Online SP.FieldUserValue.get_email() always returns NULL.
Since last week, SP.FieldUserValue.get_email() has been returning null for all users in Person or Group fields. This occures when I use getItems method. For example: var listName = "MyList"; var context = SP.ClientContext.get_current(); var web = context.get_web(); var list = web.get_lists().getByTitle(listName); var query= new SP.CamlQuery(); var items = list.getItems(query); context.load(items); context.executeQueryAsync(()=>{ var enumerator = items.getEnumerator(); while (enumerator.moveNext()) { var item = enumerator.get_current(); var fldValues = item.get_fieldValues(); console.log(fldValues["Editor"].get_email()) } }); I haven’t been able to find any information about changes related to this behavior. We’ve been using the Email property of user fields for years without any issues, and it has always worked as expected. It's documented here: https://learn.microsoft.com/ru-ru/dotnet/api/microsoft.sharepoint.client.fielduservalue.email?view=sharepoint-csom Does anyone know what might have changed or why this has stopped working?Extending SharePoint capabilities - Lightning Tools - SharePoint Partner Showcase
We are excited to share a new episode on our partner showcase series focused on SharePoint in Microsoft 365. In this post, we focus on Lightning Tools which is providing a set of additional features and capabilities directly on top of SharePoint.
Sharepoint view level permissions
Hello, I’m facing an issue in SharePoint. I have a main list where I need to create two views one for “A” users and another for “B” users. What should change is, for example, that “A” users can only see column “A” and “B” users can only see column “B”. And being sensitive data, they shouldn't be able see each other's columns. Using different lists is the only viable way I currently see this working, which i don't really want since this requires a lot more of work, unless someone can suggest a better solution. Note that currently I'm using two different pages inside the same website for user's "A" and "B". Thank you very much.AI-powered intranet solution built on SharePoint - Fresh Intranet - SharePoint Partner Showcase
We are excited to start a new blog post series focused on the different partner offerings around SharePoint in Microsoft 365. In this first post, we focus on Advania’s Fresh Intranet – an AI powered intranet solution built natively on Microsoft SharePoint.
