SOLVED-Make new contact list, have assets autopopulate to that contact
Hi everyone, I'm making a database for my company. I need guidance with one last functionality before it is ready to go to employees. I started out with the asset tracking template. I like how when you select an owner for an asset through the owner field that you can go on to that contact and see all one or more assets associated with them. So if you were to make a 2nd contact list and assign them to a different field in your asset list, how could you get that 2nd contact list to come up with all the one or more assets that one contact has just like the default contact list that comes with the template? Original post found here https://www.utteraccess.com/topics/2065439#
renamed synced site document folders - old folders are reappearing
Hello! Let me try to untangle this in words and a screenshot. The folders appearing as new folders are the old folder names. The original folders with new names are still here, but the old ones are reappearing. It says they are modified by a team member who is synced, and the modify date is several weeks ago. I'm going to guess this is a sync issue of some kind, but I can't wrap my head around how to advise a solution. Our team is new to SharePoint and this is one of about a thousand questions of how to get the team synced with our site documents without major issues. We are all mac users—does anyone know of a comprehensive resource on how to get everyone synced without these kinds of errors? Many thanks from a frazzled designer!SharePoint Online site asset file caching
Hi guys, Building an SPFx webpart for a modern team site on which the user can upload an image and crop it afterwards. Source image as well as the cropped image is stored as file in the site assets library. This is done via pnp: public ensureSiteAssetsLibrary(siteUrl: string): Promise { let web: Web = new Web(siteUrl); return web.lists.ensureSiteAssetsLibrary(); } public async uploadImage(siteUrl: string, fileName: string, blob: Blob): Promise { let siteAssetsLibrary = await this.ensureSiteAssetsLibrary(siteUrl); const shouldOverwrite = true; return siteAssetsLibrary.rootFolder.files.add(fileName, blob, shouldOverwrite); } We are referencing the img src directly via url: const fileName = "someImage.jpg"; let siteAssetsUrl = this._context.pageContext.site.absoluteUrl + "siteassets/"; let fileUrl = `${siteAssetsUrl}${fileName}`; //Can be something like: //https://foo.sharepoint.com/sites/MyModernSite/siteassets/someImage.jpg Due to the crop functionality the same image gets overwritten over and over again. When referencing to it there is some unexpected behaviour: Hitting F5 and refreshing the latest 2 or 3 versions change up each other randomly. When accessing https://foo.sharepoint.com/sites/MyModernSite/siteassets/someImage.jpg directly in the browser (with client caching deactivated through DevTools in Chrome), it is not always the latest version of the file. Just hitting F5 repeatedly and the image changes... What kind of caching is going on in the site assets? What would be the best way to truly overwrite a file without having its history? Appreciate any help, thank you! pnp/sp version: 1.2.8 Environment: SharePoint Online Modern team site