Power Platform Community Forum Thread Details

Hello there, at this very moment I'm working on a CV creator App.

One of the challenges I'm facing right now is that of creating a "Past Work Experience" and "Education" section.

For those I'm looking to add the following:

For past Work Experience

Name of Company
Period (calendar date selection)
Position
Brief description

Education section

Education type
Name of institution (also, where I can look for a "pre-made" database/list of already existing institutions ?)
Specialization
Period
Description

As you can imagine I wan those sections to be bounded to another list I've already made where is provided the Name, Email, Number of the employee. But I'd like to create more Education and Past Work entries for the same employee and I'm afraid I can't figure out a good idea/solution for both Power Apps but also SharePoint list relationships.

I'd might also ask if is possible to bound "educational institutions" to an existing list of such institutions made by someone else.

Long Story Short: I want some example, idea, explanation or overview of how to implement a multiple entry section in my Power Apps app that is bounded to an already existing list and (I'm pretty sure is going to be another list bounded to the main list).

Thank you so much and also forgive me if my English might be not that clear, I can also provide more information regarding this challenge I face, any help is appreciated!

Categories:

Building Power Apps

Hello @ZeroPowerApps ,

First of all, you must be clear about your database's relations. That's a must if you're going to work with multiple interconnected tables. If you want to create multiple "Education" for the same user, dedicate a table for all "Education" records and add a column to store the user's key.

If you store your users in a table, the key should be the ID of said table. Or, you can use a Person-type column and use the person's email as a key. The email is usually unique across AD.

On a side-note, never use LookUp-type columns, they're just confusing and actually not more useful than storing a numeric ID in a numeric column.

Next, if you want to "add new records" to a "section", you can use a gallery and add new items to its source each time you click on a button. The "OnSelect" of your button could execute either a "Collect()" or a "Patch()" to create a new record in your list.

For example, you have two tables:

Table A

Key A

Table B

Key B
Key A //Refers to 'Table A'.'Key A'

When adding a new record to the section, you "Patch()" a record to 'Table B' like this:

Patch(
 'Table B',
 Defaults('Table B'), //Create a new records with default values
 {'Key A': value}
)

The value of 'Table B'.'Key A' must be the value of the related record from 'Table A'.

Then, you display all related records from 'Table B' like this:

Filter(
 'Table B',
 'Key A' = value
)

This is more-or-less how relations work with SharePoint lists. In other words, SharePoint is actually not made for database purposes and you have to simulate their relation through Power Apps.

Hope this was helpful to you. If you need more help, don't hesitate to ask.