Please enable JavaScript.

Coggle requires JavaScript to display documents.

employee directory - Coggle Diagram

- - - - VAB - vård av sjukt barn
        
        Orange
      - Distans
        
        Blå
      - sjuk
        
        röd
      - Ledig
        
        lilla
      - Tilldela varje anställed en Enum
      - Data type
      - Kontoret
        
        Grön
        
        init value
    - - Sätt lampan som bilden
        
        När man trycker ska en drop down komma med alternative
        
        endast
  - - - No database-like data organization
        
        SharePoint doesn’t support complex data relationships typical of relational databases, such as:
        
        One-to-one. A record in one database table is related to only one record in another table. For example, a single employee can have only one ID number.
        
        One-to-many. A record in one table relates to many records in the second table. For example, one contract may relate to several business partners.
        
        Many-to-many. Each record in two tables can relate to any number of records in the other table. For example, a book can have several authors, and each author can have written several books.
        
        These relationships are impossible in SharePoint. SharePoint list item IDs can’t be used to define relationships between different list items, just unlike primary and foreign keys, specific database identifiers, can do by linking tables.
      - No large volume of items and binary data
        
        Unlike a database, SharePoint can’t handle many items. Even the SharePoint product team advises limiting the number of items in a list to 2,000 for each list container (the root of the list and any folders in the list), otherwise, the list performance significantly decreases.
      - No transaction rollback
        
        SharePoint doesn’t support the rollback of transactions. This means that in SharePoint environment, you can’t roll back changes if, for example, two changes are required to go together and the second change fails.
      - What to choose instead of SharePoint
        
        Although SharePoint rests on a database management system and has some similar functionality, the platform itself is not a database. If all you need is just structured and secure storage for several thousands of documents, SharePoint can easily meet your needs
        
        But if you need a full-fledged database with an ability to store millions of files of multiple types with an ability to manage complex relationships between items, SharePoint is not your best choice.
        
        In this regard, ScienceSoft recommends leveraging Microsoft Power Apps, a suite of low-code development software. Microsoft Power Apps enables citizen and pro developers to quickly create robust database-centric solutions. What's more, the suite smoothly integrates with SharePoint, which enables creating database apps directly from a SharePoint list.
  - - - Flow that detect when user-account is created or deleted?
        
        https://powerusers.microsoft.com/t5/General-Power-Automate/Flow-that-detect-when-user-account-is-created-or-deleted/td-p/866082
        
        Azure Logic Apps are provisioned like other Azure resources, this can be through the Azure Portal, via Azure Resource Manager (Arm) templates, Azure CLI or Azure PowerShell. There is also an extension for Visual Studio Code to help with authoring and deploying.
        
        There is no such thing as premium connectors in Logic Apps, but instead you pay per consumption, much like other Azure resources. There are a few subtle connectors that are exclusive to one or the other (e.g. Approvals are Power Automate only. More information is documented here.
        
        You can achieve this using a Webhook trigger (When a HTTP Request is Received). You can subscribe to Microsoft Graph API created and deleted change events for a User. The article below does a good job of explaining how to subscribe to Graph API events, then using Azure Logic Apps (Power Automate is Logic Apps under the hood with some minor differences).
        
        https://gotoguy.blog/2020/07/12/subscribing-to-teams-presence-with-graph-api-using-power-platform/
        
        Use Logic apps
        
        get delta
        
        graph
    - - sharepoint
        
        colunm
        
        When choice value change
        
        update data colunm.
      - Powerapps
        
        https://powerusers.microsoft.com/t5/Building-Power-Apps/Limit-User-to-One-Entry-a-Day/td-p/583739
        
        create a new list
  - - - Colunm
        
        Teams
        
        Array
        
        vab - vårdavsjuktbarn
        
        hur många som är hemma för sjukt barn
        
        Distans
        
        Hur många som jobbar hemma
        
        ledig
        
        tex
        
        grön boll - 10st
        
        kontoret
    - - Tryckbara knappar
        
        Email för att skicka email
        
        telefon så ringer man (teams ?)
        
        Meddelande på teams
      - Access lock
        
        Manger
        
        Rich text - word
        
        Medarbetar samtal
  - - - has daliy reports.
        
        Working: sick, home, or the office.
        
        saved for every month
      - one person has many reports
      - One table per month
    - - Excel table
- - - - Get group
        
        GetGroup_Response
        
        Id
        
        Description
        
        Display Name
        
        Mail
      - Get group members
        
        GetUser_Response
        
        Business Phones
        
        Display Name
        
        The name displayed in the address book for the user.
        
        Given Name
        
        The given name (first name) of the user.
        
        Job Title
        
        Mail
        
        Mobile Phone
        
        Office Location
        
        Get the users who are members of a group.
        
        Parameters
        
        Group Id
        
        Unique identifer of a group (Ex. '40639f36-46a6-73a6-91e2-9584b7913429').
      - Get user
        
        Get details for a user.
        
        Parameters
        
        User Id or Principal Name
        
        Unique identifier of a user (Ex. 'user@tennant.onmicrosoft.com' or '5f6ce5c7-b521-4842-9bbe-3f6d5aa5e35b').
        
        GetUser_Response
        
        Same as Get group members
    - - Group.ReadWrite.All
      - User.ReadWrite.All
      - Directory.ReadWrite.All
      - More information on Graph permissions and how to configure them can be found here.
    - - The connector does not return custom attributes of Azure AD entities.
      - The connector does not support Mail-Enabled Security groups.
      - AAD group with the attribute "isAssignableToRole" are not supported for now.
  - - - To use this integration, you will need access to an Office 365 mailbox that has the REST API enabled. To make a connection, select Sign In. You will be prompted to provide your Office 365 account, follow the remainder of the screens to create a connection.
      - If you see an error using the connector, please check that the REST API is enabled. Accounts on a dedicated (on-premise) mail server or accounts that are sandbox (test) accounts may also see an error. Your administrator can learn how to migrate a mailbox here. Additionally, if you are using an EWS application access policy, please ensure that the following user-agents are allowed: "LogicAppsDesigner/","azure-logic-apps/","PowerApps/", "Mozilla/"
      - Get manager action returns "No manager found for the specified user"
        .
        This happens when the user does not have a manager configured in AAD. Learn how to update an AAD user's profile to configure a manager here.
      - Get direct reports, Get manager, Get my profile and Get user profile actions declare an input parameter Select fields. You can specify a coma separated list of fields to select in this parameter (learn more about available fields here). For example:
        
        department, jobTitle
        
        displayName, surname, mailNickname, userPrincipalName
      - If the parameter is not specified, the following fields are selected by default: aboutMe, accountEnabled, birthday, businessPhones, city, companyName, country, department, displayName, givenName, hireDate, id, interests, jobTitle, mail, mailNickname, mobilePhone, mySite, officeLocation, pastProjects, postalCode, preferredLanguage, preferredName, responsibilities, schools, skills, state, streetAddress, surname, userPrincipalName, userType.
      - Conditional Access policies can prevent the connector from running as expected. Example of an error: "AADSTS53003: Access has been blocked by Conditional Access policies. The access policy does not allow token issuance.". Please refer to Azure AD Conditional Access documentation for more details.
      - Get my profile (V2) action may fail with 401 Unauthorized error when used by guest users. To workaround this, try specifying Select fields parameter explicitly to: id, displayName, givenName, surname, mail, mailNickname, accountEnabled, userPrincipalName, department, jobTitle, mobilePhone, businessPhones, city, companyName, country, officeLocation, postalCode.
- - - - powerautomate
        
        every month take (komptid etc,) to excel(busniess).
- - - - Role/Access (Access Control List - ACL) in SharePoint
        
        Step 1 - Create a SharePoint list for your ACL
        
        I'd recommend that general users ONLY have read access to the list - they must have at least that permission.
        
        Call it what you want
        
        AppACL
        
        Step 2 - Put the following Columns in the SharePoint AppACL list
        
        UserEmail Text Column (you can rename Title to this if you want, just remember it is still technically "Title")
        
        HasManagerRole - A Yes/No column
        
        Step 3 - Add a record (or more) in the SharePoint AppACL list with the email address of the people you want to have access. Set the HasManagerRole to Yes for them.
        
        By nature of this solution, you don't have to add people who would NOT have a manager role, only those that do
        
        Step 4 - In your PowerApps app, create a connection to the AppACL list.
        
        Step 5 - In your OnStart (best place for it, but you can do elsewhere if necessary) place the following Formula:
        
        Set(MyACLprofile, Lookup(AppACL, Title = User().Email))
        
        //remember from above if you renamed Title to UserEmail, it's still title. If you added another column for the email address, then use that instead of Title (sharepoint columns)
        
        Use Office365Users.MyProfile().Mail instead
        
        Step 6 - Anywhere you want to control a property based on the permission in the ACL, use the formula:
        
        MyACLprofile.HasManagerRole
        
        So, for your needs, on the DataCard for the field you want to hide from everyone except those with access, set the Visible property to (MyACLprofile.HasManagerRole)
        
        That's all there is. You can now control the datacard visibility (and any other control you set this on) from your SharePoint ACL list.
    - - A choice from a set of options, backed by a number. This data type combines a localizable text label with a numeric value. The label appears in the app, and the numeric value is stored and used for comparisons.
      - ThisItem.OrderStatus
      - https://docs.microsoft.com/en-us/power-apps/maker/canvas-apps/functions/data-types#choices-and-yesno
      - Create a choice
    - - Data
        
        Tables
        
        Choices
        
        The Choices function returns a table of the possible values for a lookup column. Use the Choices function to provide a list of choices for your user to select from. This function is commonly used with the Combo box control in edit forms
- - - - Ja / nej
    - - Ja / nej