Video summary

Power Apps (Control de Stock) - Video 2

Main summary

Key takeaways

Technology

Main technological concepts / workflow

  • Use Office 365 / Power Apps development environment: Development happens inside the Office 365 platform. Access is provided via office.com / office365.com.
  • Create and use a SharePoint data source for Power Apps: Power Apps uses SharePoint lists hosted in the same Office 365 tenant as the backing database.

Step-by-step product features / how-to (SharePoint setup for Power Apps)

  1. Open Office 365 Admin/App menu

    • In Applications, locate Power Apps and SharePoint.

  2. Create a SharePoint site to store data

    • Create a new SharePoint communication site (chosen for easier sharing across the organization).
    • Configure language (Spanish is shown in the example) and create the site.
    • This site becomes the cloud space where the app’s data will live.

  3. Create SharePoint lists (tables) as the data source

    • From the site’s Site contents, create lists representing entities needed by the stock control system.
    • List created from scratch (example: Users)
      • Add columns using SharePoint data types:
        • username: single line of text, max ~30 chars
        • key/password: single line of text, max ~50 chars
        • permissions: single line of text, max ~20 chars
      • Note: SharePoint requires a built-in Title column; it must exist even if not used directly.

  4. Alternative list creation: import from Excel

    • The tutorial demonstrates importing tables from an Excel workbook into SharePoint.
    • Key concept: Excel tables include an “extra” field.
      • This “extra” field maps to SharePoint’s required Title column, allowing the real dataset columns to remain separate.
    • Example imported lists/entities:
      • Products table with fields like:
        • stock (numeric), cost/number (numeric), retailer/wholesaler/category (numeric), commission (numeric)
        • image (multi-line text type)
        • plus the “extra” → Title mapping
      • Officials table with fields like:
        • ID card, name, address, telephone, cell phone (text)
    • SharePoint’s internal ID is handled automatically and doesn’t need to be manually modeled in columns.

  5. Reconfigure and manage list columns

    • After import, open each list and edit column settings (for example, adjust maximum character lengths for fields like ID card and phone numbers).

  6. Permissions model (site access + list-level permissions)

    • Use Site access roles:
      • Owners, Members, Visitors
    • The video emphasizes permission control, including:
      • inheriting or stopping inheritance from site-level permissions
      • restricting permissions for specific roles (e.g., remove permissions so users can’t even see the list)
    • It also highlights controlling permissions for the SharePoint list itself—not only how Power Apps behaves.

Key takeaways

  • Power Apps uses SharePoint lists as a data source.
  • SharePoint lists can be created:
    • manually (define fields/columns), or
    • by importing from Excel (recommended for preloading structured data).
  • Because SharePoint requires a Title column, the workflow uses an “extra” Excel column mapped to Title.
  • The tutorial focuses on robust permission configuration, including stopping permission inheritance and managing access per list/role.

Main speakers / sources

  • Speaker: Not explicitly named in the subtitles (presenter/teacher guiding through Office 365 + SharePoint).
  • Primary sources referenced: Microsoft Office 365, Power Apps, SharePoint, and Excel.

Original video