I see how to do basic crud operations on CRM entities using Logic Apps. Is there a way to create a relationship between two entities? In a one -> one, one -> many and many -> many cases?
Thanks.
Yes. What you're probably looking to use is the AssociateRequest message which is it's own Entity in the SDK.
You will likely have to work with the owners of CRM on specific details.
Related
I've been tasked with setting up FreeIPA for my company. What we are looking to do is have multiple "admins" that can only manage and see the users that belong to their team. For example, we have three organizations in our company orgA, orgB, orgC. I want to appoint a manager from orgA to be able to create and edit users and groups that belong to orgA, but not be able to see anything that belongs to orgB or orgC. I found some documentation on the FreeIPA website, but it only appears to be a concept?
If anyone else has accomplished this or can confirm that it's just not possible, that would be helpful.
There is no support for multitenancy in FreeIPA and there is no plan to implement it. Separate organizations need their separate deployments.
I want to use a graph database for a web application (involving a web of Users, Posts, Comments, Votes, Answers, Documents and Document-Merges and some other transitive relationships on Users and Documents). So I start asking myself if there is something like a design methodology for Graph Databases, i.e. a kind of analogon to the design principles recommended for Relational Databases (like those normal forms)?
Example questions (of many questions arising):
Is it a good idea, to create a Top-Node Users, having relationships ("exist") on any User-Node in the Database?
Is it a good idea to build in version management (i.e. create relationships (something like "follows")) pointing to updated versions of a Document / Post in a way that going back this relationship means watching the changes the document went through.
etc...
So, do we need a Graph Database Design Cookbook?
The Gremlin User Group (http://tinkerpop.com/) and Neo4j User Group (https://groups.google.com/forum/?fromgroups#!forum/neo4j) are good places to discuss graph-database modeling.
You can create supernodes such as "Users," but it may be better and more performant to use indexes and create an index entry for each user with a key=element_type, value="user", id=user_node_id.
A "follows" relation is often used for people/friends like on Facebook and Twitter so I wouldn't use that for versioning. You can build a versioning system into to Neo4j that timestamps each entry and use a last-write wins algorithm, and there are other database systems like Datomic that have this built in.
See Lightbulb's model (https://github.com/espeed/lightbulb/blob/master/lightbulb/model.py) for an example blog model in Bulbs/Python (http://bulbflow.com).
I have a Yahoo! Group that has its own Database tables for various reasons. I'd like to create a mobile application (or web app) that performs CRUD operations on such tables. Does anyone have any clue as to how I can get started on learning how to do this (if at all?)
Unfortunately, Yahoo! Groups does not have an external API. But, you might be able to use Export Table functionality which delivers the database records in CSV format.
I'm building a database
where users will access the same table but they cannot edit each others records.
I'will be using views+insert/update/delete stored procedures from my .NET application.
What's the best way to achieve safe acess to tables?
It sounds like you're building a sort of a multi-tenant application. For my 10 cents it's better to handle this authorization within your application code. There's a couple of MSDN artlcles at the link below about architecture for these sort of systems:
http://msdn.microsoft.com/en-us/library/aa479086.aspx
You can change their security options and disable access to the base tables. You can then do all of your IO through either stored procedures or views.
For example you make a view for company A and another for company B, company A only has rights to see their view and so on.
What are the Tables that would be present in a social networking site (ex: Twitter).
I have a users table as of now. How to keep track of followers and people I do follow?
Should I maintain a separate table for followers and people I follow?
What are the columns which would be there in those tables?
Please don't think this as Subjective/Off topic. As I am a beginner, I thought experts can guide me to get a good DB design?
Try having a look at Database Answers in particular the data models. They have several different designs for various systems. This one is for a social networking site which may give you an idea of what's required.
You may want to search on SO for other social network database questions. I found this one that had a link to flickr showing a schema which appears to be from Facebook.
Your database design will be based around your system requirements. Without knowing exactly what you are trying to achieve, it is difficult to give you the best design.
you can use this Messenger Database Design Concept: Messenger DB
You can create a separate table for follower/ followed relationships. So, when x follow y, create an entry with follower_id = x.id followed_id = y.id.
You can query the relationship table to look for all the users x has relations with by select * from relationships where follower_id = x.id or vice versa.
When/if x un-follow y, you just have to delete the entry you originally created.