Viktor Lázár

Hi @Jscott388, the JayData entity definition format is not compatible with odata-v4-server. JayData is an ORM, but odata-v4-server is only a generic OData server implementation. You have to convert the...

Hi @jacek-lapinski, this model is working as expected: https://github.com/jaystack/odata-v4-server/blob/master/src/example/model.ts Category EntityType includes `````` How you implemented your model? How you used the decorators to annotate the OData types?

Hi @egarim, odata-v4-server is a platform independent generic OData server and you can implement any business logic in the controllers. Connectors are specific OData query compilers, which are transforming the...

@egarim: you should target the index.js (lib/ts/index.js in the examples) or the main entry file for your server and should use the correct port by using ```process.env.PORT```. odata-v4-server examples are...

> We don't have strong recommendation for Node builds. There's different tradeoffs depending on if you use a warm server or cold starts. It's also less sensitive because the downstream...

You can install the latest JayData CTP from npm with `npm install jaydata@next`. On the client side, you have to use the client odatajs script file. You can find it...

Hi, just published [odata-server](https://www.npmjs.org/package/odata-server) 1.3.7 supporting Express 4 to the npm registry. It's a much better and easier way to publish your OData service. Read more about JayData Server here:...

Sorry for being so late with the webpack support fix, please update JayData to latest version from npm (1.5.10). You have to include the json-loader in the webpack config file....

Just `require("jaydata/odata");` (or `import "jaydata/odata";` in TypeScript) before you import your generated context.

Hi @Randy85253, the odata-v4-metadata library works with the Olingo odatajs library JSON format, which is transforming the metadata XML document to JSON and changing all property names to lowerCamelCase. odata-v4-metadata...