Skip to content
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

Bad Request - Resource not found for the segment 'columns' #947

Closed
justinrogowski opened this issue Dec 12, 2024 · 2 comments
Closed

Bad Request - Resource not found for the segment 'columns' #947

justinrogowski opened this issue Dec 12, 2024 · 2 comments
Labels
Status: No recent activity status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close type:bug A broken experience

Comments

@justinrogowski
Copy link

Describe the bug

I am trying to add a new column to a SharePoint Embedded container using C# and when running the code obtained from here I am getting a Microsoft.Graph.Beta.Models.ODataErrors.ODataError with the message "Bad Request - Resource not found for the segment 'columns'". Other endpoints such as creating a Container work fine when called from the same GraphServiceClient.

Expected behavior

The column is successfully created and no error occurs

How to reproduce

`var requestBody = new ColumnDefinition
{
Description = "test",
EnforceUniqueValues = false,
Hidden = false,
Indexed = false,
Name = "Title",
Text = new TextColumn
{
AllowMultipleLines = false,
AppendChangesToExistingText = false,
LinesForEditing = 0,
MaxLength = 255,
},
};

// To initialize your graphClient, see https://learn.microsoft.com/en-us/graph/sdks/create-client?from=snippets&tabs=csharp
var result = await graphClient.Storage.FileStorage.Containers["{fileStorageContainer-id}"].Columns.PostAsync(requestBody);`

SDK Version

5.88.0

Latest version known to work for scenario above?

No response

Known Workarounds

No response

Debug output

Click to expand log ```
</details>


### Configuration

Windows 11, x64

### Other information

_No response_
@justinrogowski justinrogowski added status:waiting-for-triage An issue that is yet to be reviewed or assigned type:bug A broken experience labels Dec 12, 2024
@andrueastman
Copy link
Member

Thanks for raising this @justinrogowski

Any chance this is still an issue on your end using the latest version of the client?
Please note that APIs on the beta endpoint can change and be removed and shouldn't really be used in production environments.

@andrueastman andrueastman added status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close and removed status:waiting-for-triage An issue that is yet to be reviewed or assigned labels Feb 4, 2025
@baywet baywet added status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close and removed status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close labels Feb 4, 2025
Copy link
Contributor

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: No recent activity status:waiting-for-author-feedback Issue that we've responded but needs author feedback to close type:bug A broken experience
Projects
None yet
Development

No branches or pull requests

3 participants