Comments (12)
If connecting with the v3 logic works, then perhaps that is all you need to do, according to the docs,
The Business Central implementation of EDM follows the .NET 4.0 WCF Data Service Framework implementation.
Which approximates and older preview of the OData v4 specification. We really need to see those screenshots to help more, perhaps you can use another forum like www.stackoverflow.com to post your issues there and link back to this issue, with that or upload your images to a public host and paste in the links.
from unchase.odata.connectedservice.
Hi, @ajithnairms
Did you use Network Credentials
or Web Proxy
credentials?
Also try to uncheck Add code templates (Whether to include the T4 files into this project)
.
from unchase.odata.connectedservice.
from unchase.odata.connectedservice.
from unchase.odata.connectedservice.
from unchase.odata.connectedservice.
Hi.
I can't see all the screenshots. You should send them from email directly (not from github).
from unchase.odata.connectedservice.
I had replied directly from mail along with screenshots.
I cant paste it here.
from unchase.odata.connectedservice.
By unchecking below option , it does not work at all and gives the same error that I shared initally.
Add code templates (Whether to include the T4 files into this project).
from unchase.odata.connectedservice.
I have the same problem. The thing is, with network credentials, the extension adds Authorization
header (after getting 401) the first time - when I click "Next" button - but doesn't add it the second time - when I click "Finish" button to actually generate stuff.
from unchase.odata.connectedservice.
I have the same problem. The thing is, with network credentials, the extension adds
Authorization
header (after getting 401) the first time - when I click "Next" button - but doesn't add it the second time - when I click "Finish" button to actually generate stuff.
Have you tried to download the metadata file, and use it locally to generating client code?
from unchase.odata.connectedservice.
I have the same problem. The thing is, with network credentials, the extension adds
Authorization
header (after getting 401) the first time - when I click "Next" button - but doesn't add it the second time - when I click "Finish" button to actually generate stuff.Have you tried to download the metadata file, and use it locally to generating client code?
No. After seeing that the client does not send the Authorization
header, I just allowed anonymous access for a while. That allowed me to continue.
from unchase.odata.connectedservice.
Hi, @ziacik
At the moment, I am focused on improving the Connected service by Microsoft and actively contribute to it, since its development has resumed. All features will be transferred to this project. In addition, it is developing faster, so all new features will be added there.
You can create your issues in this repository.
from unchase.odata.connectedservice.
Related Issues (20)
- Issue with VS Pro 2022 - 17.2, No context menu option to update/run. HOT 6
- Error to generate client HOT 1
- Missing [global::Microsoft.OData.Client.ContainerProperty] on DynamicProperties HOT 2
- Cannot connect to ODATA v4 from MS Business Central via Visual Studio for Outh authentication HOT 2
- Error while adding service. HOT 1
- BUG - Adding Unchase OData Connected Service to the project failed: Type PrimitiveType is unrecognized
- Ignore entities without primary key
- FEATURE Generate Multiple Files HOT 1
- Edmx with whitespace in property names causes generation of invalid C# code HOT 1
- Generation never run
- DOC
- The Nuget Package System.ComponentModel.Annotations is always added HOT 1
- ARM64 Support HOT 1
- Exception in property changed event
- Can't call metadata urls that require oAuth header HOT 3
- Annotation tag in metadata.xml causes parsing EntityName error
- Error:Adding Unchase OData Connected Service to the project failed: Cannot write to a closed TextWriter. HOT 2
- thank you HOT 1
- Using a metadata xml with multiple objects with the same names gives errors HOT 1
- Error:Adding Unchase OData Connected Service to the project failed: The 'Name' attribute is invalid - The value '3_2' HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from unchase.odata.connectedservice.