Forum Widgets
Latest Discussions
Sharepoint SitePage
Using Graph API . I want to access a specific Sitepage , I need to know the Sitepageid, based on /pages it will return all Page id within the Site, Is there a way to get the Sitepage id directtly based on the Sitepage name.aspx ? I want to detect files changes on that Sitepage and be able to downlaod the files from the sitepage ? How can we do that using Graph API I know we can detect files changed at the drive level within a site. I am looking for Sitepage can we do the same ?what API can be used ?Girish_venkataramanappaOct 03, 2025Copper Contributor12Views0likes0CommentsRepository structure and CI/CD pipeline for SPFx WebParts
I am currently developing SPFx WebParts for a single SharePoint site. In our development repository, I have: A shared SPFx library Six separate WebParts, each in its own solution, organized as follows: library webparts webpart1 webpart2 webpart3 ... At the moment, on Azure DevOps, everything is managed in a single repository. To build and deploy a WebPart, I check Git for changes, build the WebPart, and then deploy it. I am considering whether, for the CI/CD pipeline, it might be more efficient to adopt a separate repository for each WebPart, allowing independent pipelines for each solution. In this scenario, I have two main questions: Is it considered a best practice to separate WebParts into distinct repositories? How should the shared SPFx library be managed in this case? I assume it would need a separate repository, but I would like guidance on the best way to integrate it with the WebParts. Thank you for your support.rosamartinamilazzo25Sep 18, 2025Copper Contributor18Views0likes0CommentsHaving issues with SPFx isolation build lately
Hello We have a customer using an isolation version of our product and when we built a new version last week, it stopped working with below error. Unfortunately, once we install the new build, replacing with the older ones that used to work stopped working and showing the same error. "authorize:90 Unsafe attempt to initiate navigation for frame with origin 'https://xxxx.sharepoint.com' from frame with URL 'https://login.microsoftonline.com/..........'. The frame attempting navigation of the top-level window is sandboxed, but the flag of 'allow-top-navigation' or 'allow-top-navigation-by-user-activation' is not set" We would really appreciate how to handle these errors. Thanks VijayVijaydeepSep 02, 2025Copper Contributor17Views0likes0CommentsAccessing endpoints published to Entra Application Proxy from SPFx
We have an on-premises web service (hosted in IIS) published through Entra Application Proxy. When attempting to access the published endpoints from a SharePoint (SPFx) web part, we encounter CORS errors (302 Found). Accessing these endpoints directly from a browser address bar works as expected. In IIS, the Access-Control-Allow-Origin response header is set to * (wildcard). We have also tried specifying a particular domain, but that did not resolve the issue. Pre-authentication is enabled in Entra Application Proxy. Has anyone successfully connected to endpoints behind Entra Application Proxy from an SPFx web part? Any insights or solutions would be greatly appreciated.jyamauchiJun 20, 2025Copper Contributor64Views0likes0CommentsSharepoint Basic auth authentication effect SharePointOnlineCredentials?
I'm wondering if the announcement of Basic auth deprecation for SP online mentioned here https://learn.microsoft.com/en-us/sharepoint/technical-reference/basic-auth-is-being-deprecated affects the use of the SharePointOnlineCredentials method of logging in via .net CSOM APIs. I'm aware it takes username and password but I thought it was actually classified as a form of Claims Based Authentication not basic. I know on the client side, newer CSOM libs don't include that structure any more. But that doesn't mean the server will no longer accept that means of login. The object I'm talking about is https://learn.microsoft.com/en-us/dotnet/api/microsoft.sharepoint.client.sharepointonlinecredentials.-ctor?view=sharepoint-csom&devlangs=csharp&f1url=%3FappId%3DDev16IDEF1%26l%3DEN-US%26k%3Dk(Microsoft.SharePoint.Client.SharePointOnlineCredentials.%23ctor)%3Bk(TargetFrameworkMoniker-.NETFramework%2CVersion%3Dv4.8)%3Bk(DevLang-csharp)%26rd%3Dtrue And the means of using it would be like this SharePointOnlineCredentials creds = new SharePointOnlineCredentials(sUserName, securePassword); ClientContext ctx.Credentials = creds; string authCooke = creds.GetAuthenticationCookie(Sharepointuri);dgrillo2025May 22, 2025Copper Contributor55Views0likes0CommentsWebpart theme colors not working for border-color
I've got a strange situation were using the following works with background-color but not border-style. // works as expected - picks up the current themeLight color from the site. background-color: "[theme:themeLight, default: #c86c70]"; // doesn't work as expected - ALWAYS picks up the default color - not the themeLight color. border-color: "[theme:themeLight, default: #c86c70]"; Is any one else seeing this? Not sure if it's due to the latest version of SPFx (1.21)? If so, I'll log another bug.GrantJenkinsMay 02, 2025Copper Contributor42Views0likes0CommentsFailed to get FormDigestValue with 403 Forbidden in java
Hello Everyone, This is my first time to access sharepoint via java in my project. I used AI to get varies of java code and try to connect to sharepoint to get FormDigestValue as step one (The target is to upload files). Somehow it always return 403. Could you please help to figure out the root cause? I appreciate for any comments. I struggle with the problem for several days already. Code 1: System.setProperty("sun.net.http.allowRestrictedHeaders", "true"); URL urlRequest = new URL(siteUrl + "/_api/contextinfo"); HttpURLConnection contextInfoRequest = (HttpURLConnection) urlRequest.openConnection(); contextInfoRequest.setRequestProperty("Content-Type", "application/json;odata=verbose"); contextInfoRequest.setRequestProperty("Accept", "application/json;odata=verbose"); contextInfoRequest.setRequestProperty("Connection", "Keep-Alive"); contextInfoRequest.setRequestProperty("Content-Length", "0"); contextInfoRequest.setDoOutput(true); contextInfoRequest.setRequestMethod("POST"); String authStr = username + ":" + password; String encodedAuthStr = Base64.getEncoder().encodeToString(authStr.getBytes()); contextInfoRequest.setRequestProperty("Authorization", "Basic " + encodedAuthStr); contextInfoRequest.connect(); InputStream in = contextInfoRequest.getInputStream(); -- 403 here Code 2: System.setProperty("sun.net.http.allowRestrictedHeaders", "true"); URL urlRequest = new URL(siteUrl + "/_api/contextinfo"); HttpURLConnection contextInfoRequest = (HttpURLConnection) urlRequest.openConnection(); contextInfoRequest.setRequestProperty("Content-Type", "application/json;odata=verbose"); contextInfoRequest.setRequestProperty("Accept", "application/json;odata=verbose"); contextInfoRequest.setRequestProperty("Connection", "Keep-Alive"); contextInfoRequest.setRequestProperty("Content-Length", "0"); contextInfoRequest.setDoOutput(true); contextInfoRequest.setRequestMethod("POST"); Authenticator.setDefault(new Authenticator() { @Override public PasswordAuthentication getPasswordAuthentication() { return new PasswordAuthentication(domain + "\\" + username, password.toCharArray()); } }); contextInfoRequest.connect(); InputStream in = contextInfoRequest.getInputStream(); -- 403 here Code 3: // Create the SharePoint context HttpClient client = createHttpClient(); String authHeader = getBasicAuthHeader(shareac, sharepw); // Example request to SharePoint HttpRequest request = HttpRequest.newBuilder().uri(URI.create(galurl + "/_api/contextinfo")) .header("Authorization", authHeader) .header("Accept", "application/json;odata=verbose") .POST(HttpRequest.BodyPublishers.ofString("")) .build(); HttpResponse<String> response = client.send(request, HttpResponse.BodyHandlers.ofString()); System.out.println("Response Status Code: " + response.statusCode()); -- 403 here Code 4: // 设置SSL协议 SSLContext sslContext = SSLContext.getInstance("TLSv1.2"); sslContext.init(null, null, null); HttpsURLConnection.setDefaultSSLSocketFactory(sslContext.getSocketFactory()); // 创建HttpClient CredentialsProvider credentialsProvider = new BasicCredentialsProvider(); credentialsProvider.setCredentials(new AuthScope(galurl, -1, AuthScope.ANY_REALM), new UsernamePasswordCredentials(shareac, sharepw)); CloseableHttpClient httpClient = HttpClients.custom() .setDefaultCredentialsProvider(credentialsProvider) .build(); // 使用httpClient进行请求 // 示例:发送GET请求 HttpGet httpget = new HttpGet(galurl); HttpResponse response = httpClient.execute(httpget); // 处理响应 int statusCode = response.getStatusLine().getStatusCode(); System.out.println("Response status code: " + statusCode); -- 403 hererickyhuang2025Mar 31, 2025Copper Contributor59Views0likes0CommentsHow to get list items from one SharePoint tenant to another SharePoint tenant
Requirement: We have developed task management solution which can be deployed at any SharePoint site and I wanted to pull tasks from SharePoint site in different tenant to my tenant SharePoint site and show them in task dashboard. We have used SharePoint Framework (SPFx) to develop this dashboard, and we are ready to accommodate any other technology also if that fulfills requirement. Please suggest if this is possible to do and what should be approach? Thanks, DeepakDeepak1981Mar 26, 2025Copper Contributor44Views0likes0CommentsIssue with SharePoint Add-in Uninstalling After Renaming App Web url
We are migrating customers from the retired SharePoint Add-in model to the new SPFx model. As part of this, we automatically rename the App Web (created during Add-in installation) and changing its URL and create a new subsite with the original App Web’s name & URL to host the SPFx app and its content. However, when the customer later uninstalls the Add-in, SharePoint deletes the new subsite instead of the original App Web, which still exists under its renamed URL. This suggests that the installed Add-in is not aware of the App Web renaming/changed URL, causing it to target the wrong site for deletion. Our migration process relies on preserving existing links by maintaining the original App Web URL for the new subsite. Is there a way to update the installed Add-in to recognize the renamed App Web? Alternatively, is there a recommended approach to prevent the unintended deletion of the new subsite when the Add-in is uninstalled?Ross_CullenMar 21, 2025Copper Contributor43Views1like0Comments
Resources
Tags
- developer1,245 Topics
- PnP648 Topics
- apis491 Topics
- Extensibility253 Topics
- Responsive128 Topics
- hybrid82 Topics
- SPFx70 Topics
- SharePoint Online64 Topics
- powershell23 Topics
- SharePoint Online Office 36515 Topics