How to create Ocelot Api with EF Navigation Property? - ocelot

I have a question.I have two api Product.Api and Customer.Api with OcelotApiGetaway.Product.Api and Customer.Api are used common MSSQL Database.
How to bind Product Entity and Customer Entity with navigation property ?
Because Product Entity created in Product.Api and Customer Entity created in Customer.Api.
Thanks

Related

How to update multiple entities in Cuba Platform Frontend UI

I have a function that returns data from many entities and puts them in a table. When the table is changed and the save button is clicked I need to send all the data to their entities. Is there a way to do this in one action?
If you mean that you need a REST API method which can update several entities at once - then there is no such built-in method in the CUBA REST addon.
However, backend developers can create and expose a "service method" for you that accepts list of entities or POJOs as parameter. Then you will be able to call it from the web page.
See https://doc.cuba-platform.com/restapi-7.2/#rest_api_v2_ex_service_post

Create custom fields for Invoice in Dynamics 365 Sales

Hello I'm new to Dynamics, and I'm interested if there is a way to add a custom fields inside Invoices entity. I have seen that there is a way to create a new entity inside Sales, but I need to еxpand the Invoices entity in particular since the other fields in there are useful for me.
Creating a New Invoice
Yes, you can add custom fields inside any standard or custom entity in a Dynamics 365 / Power Apps instance.
This is the documentation link to check https://learn.microsoft.com/en-us/powerapps/maker/data-platform/create-edit-fields

How to call attributes of a database record in a Shopware 5 form

I'm not familiar with Symfony or VueJS. I have an id of a table in a Shopware 5 form, how can I access the attributes of that record?
Do you use Shopware5 or Shopware6?
Shopware 5 uses Smarty in the storefront and ExtJS in Admin.
Shopware 6 is build with Twig and VueJs.
If you want to access data from the database I'd recommend doing this in PHP and use the Repository of the Entity.
If you need the data in a specific view you could use a subscriber (explained here).

Right way to model relationship in Entity Framework Core

I'm working on an ASP.Net Core MVC 2.0 application using Entity Framework Core 2.0. I need to upload a file related to an entity that is getting created by this application.
For example, imagine having to upload an invoice PDF as part of creating a payment entity. This should be a one-to-one relationship.
I'm having some trouble deciding how this should be represented in the Entity Framework data (and object) model. I found some guidelines that say that the entity foreign key should exist on the dependent object. In this case, the invoice would be the dependent object, so I should add the payment ID to the invoice object.
But I won't be downloading the invoice object as often as I would the payment object. And I was planning on a flow where the payment view would have a link to an action on the invoice controller to download the invoice using the invoice ID. So having the Invoice ID on the Payment object would make sense.
So I'm not sure of the best way to handle this.
As an aside, I've seen plenty of samples with uploading/downloading files, but not many that shows them how this might look when the files are associated with an entity in the database.
Does anyone have any suggestions?
I don't have any code that I can share at the moment; if anyone thinks code might help, I can throw something together.
Thanks in advance!
Just wanted to point out that Gert Arnold's comment was the correct answer; the following has examples of how to model one-to-one relationships.
https://learn.microsoft.com/en-us/ef/core/modeling/relationships
Thanks Gert!

fluent nHibernate and relation to Asp.net Membership tables

I'm using fluent nHibernate (automapper) and at the same time use Asp.net Membership, but how do i reference aspnet_Users table?
maybe create a new user table with only the ProviderUserKey as field? and always make references to that table? and use Membership.GetUser(..) to get name etc.
You should implement new Membership provider with NHibernate.
But...why do it if someone else did it already...
http://www.google.com/search?hl=en&q=nhibernate%20membership%20provider&btnG=Search
Use Windows Identity Foundation (WIF) and abstract away the whole authentication thing.
http://blogs.msdn.com/card/archive/2009/11/18/windows-identity-foundation-wif-rtm-announced.aspx