I'm researching for sharing data from Parent Company to another child company and has read 2 blog below but I don't know that how It's work and how can I implement it.
This is the link of blog:
Company Mask
Group Mask
What I'm expecting is share data about Inventory or User or anything else to another company because I just want to use 1 product for all company.
Is there any ideas to use Company mask and Group mask to share data to another company?
Thanks for reading and thanks for your help!
For sharing data between tenants (companies), CompanyMask is the field. GroupMask is for restriction groups and is to do with row level permission within a tenant. There is an old but very effective blog post here: https://blog.acumatica.com.sg/2013/05/understanding-company-setup-options.html that talks about it in great detail that should get you what you want.
Related
When asking for a token in a custom account creation process, if we do not set business_type, it is possible, using Onboarding, to set your Business Type later.
What is the correct answer for an Association in France ?
Individual / micro-entreprise
Company
Associations can have a SIREN (unique French business identification number). But not all associations have one.
If we choose type 1, we do not have to fill for a SIREN, but then my question is: will it be a problem later for payouts ?
I contacted the support. OnBoarding does not provide an option for custom accounts and associations.It is a work in progress.
I am wondering how to keep track of the owners assets. I don't think having an asset called 'stock' would be very effective in this regard, because that would not seem like the blockchain way.
Let say you are sending a shipment with Product asset to another owner. This owner needs to accept the shipment of products. When he accepted it should I add these products to an inventory asset of that owner?
The other option is when the new owner accepted the shipment, do nothing. And when the owner wants to know his inventory he queries all the shipments with his signature to get the ID of the assets he owns.
I suggest you reading the official Commercial Paper Tutorial which is similar to what you're trying to do.
https://hyperledger-fabric.readthedocs.io/en/release-1.4/tutorial/commercial_paper.html#
I'm little bit confused about when to create a new entity in rest. I have this rest api implemented in node:
GET api/v1/services - get all services
GET api/v1/services/{serviceId}/suppliers - get all suppliers for service id
Now, I want to add another api for getting all suppliers, no matter which service.
Does the following approach is good practice?
GET api/v1/services/suppliers - get all suppliers
PUT api/v1/services/suppliers/{supplierId} - edit by supplier id
Or should we need to create a new suppliers entity?
I hope that #wizard already found an answer for his question.
But here are my thoughts.
As per my understanding, the resource "api/v1/services/suppliers" is not a right way to get back all the suppliers. We can use the REST Subresources to represent the relationships so that it will be more readable one. But here Supplier resource can't be used outside of parent resource(Services).
But in this case, we want to get all supplier details and also update the specific supplier information. Hence we require a flexible API. So we have to create another endpoint(/api/v1/suppliers) for working with supplier details.
(/api/v1/suppliers - fetch all the supplier details(GET)
and
/api/v1/suppliers/{supplierId} [PUT] for updating a specific supplier.
I'm thinking to use DDD for our next application. I have already found a lot of interesting papers and answers but cannot find a solution to my problem :
We have an SOA. architecture where some services are known as master of their datas. That's nice but I can't figure how to use them nicely with DDD.
Given a service "employees" who is the master of the Employee datas, it is a crud over a couple of simple values (first and lastname, birthdate, address).
My new app, should track the trainings offered to those employees. So I have the concept of Participant, a Participant has the same values as an Employee plus a list of trainings and a skill.
We can suppose that the "trainings" applications has a database with a table of participants that contains a participant_id, skill and one employee_id used to retrieve the first and lastname.
Am I correct ?
But now, which component may I use to call the "employees" service ? Is it the ParticipantRepository so that when I get a participant I have is names. Or is it the application service who complete the Participant datas before using them. Or may I explicitly call the employees service when needed ?
Thanks a lot.
In your training application (I mean in the domain of your application) the concept of an employee might not exist as other than an external reference. As you correctly said, that will be a Participant.
I understand that you need to get some data from the employee service to populate the participant. I can think of few options.
1) ParticipantRepository builds a Participant, which is an aggregate root, some of that data might be in a PersonalDetails value object. This value object is constructed by calling the employee app. This approach is easy, but might not be the best. This is the approach you mentioned, where the ParticipantRepository calls an interface PersonalDetailsService and the implementation of that interface does the actual call to the Employee service. In this way, your domain has no idea that is dealing with employees, as it only sees PersonalDetails.
2) Eventual consistency by replicating data from the employee service: If the employee service can send a notification when an employee is updated (e.g. via messaging) you can listen to those events and have a read only copy of the data. The benefit of this is that your app will work even if the employee service goes down. The problem is that you might need to build something to re-send data that might have got lost.
Both of these approaches are explained quite well in the book Implementing Domain-Driven Design
I found a couple references but quite very old and I know the API has changed since.
Are all resources IDs globally unique (across all accounts)?
For instance are all to-do item IDs unique accross all accounts in the system ?
I want to know as i would like associate data with a to-do ID and i want to make sure to avoid collisions (as unlikely as they could be)
EDIT:
Here is a sample ID: 8549954
One of the post i referred to: https://groups.google.com/forum/#!searchin/37signals-api/ID$20unique/37signals-api/cNm-HKZ5fQY/xi497xpem1AJ
Thanks for clarifying.
They are unique across accounts, within the same product. So, for all requests to the Basecamp API (https://github.com/basecamp/bcx-api), you can treat the resource IDs as unique.