Power Apps Specialist for PepsiCo Peru
Budget: $30 – $250 USD
The Supply Chain department at PepsiCo Peru is seeking a specialist in Microsoft Power Apps, Power BI, Excel, and SharePoint to implement a data integration and synchronization solution between Excel files and an application developed in Power Apps. The objective of this project is to improve the recording and tracking of operational process times within the Logistics and Warehousing department through the use of integrated digital tools.
**Project Context**
We currently utilize an Excel file in XLSM format, which contains macros and operational logic used by the team. This file is stored on SharePoint and constitutes an integral part of the department's workflow.
To enable integration with Power Apps, it is necessary to design and build an architecture that allows for data entry via the application without compromising the functionality of the existing macros.
**Solution Structure**
The solution must incorporate the following elements:
• Maintain the original Excel file—including macros—in XLSM format as the primary file.
• Create a structurally identical copy of the file in XLSX format.
• The XLSX file will serve as the data source utilized by Power Apps.
• Both files will remain hosted on SharePoint.
**Integration with Power Apps**
It is necessary to implement the logic required to enable Power Apps to record or modify data within the XLSX file.
This will allow users to log hours or other operational events using buttons or forms embedded within the application. The XLSX file will function as an integration layer bridging the application and the XLSM file.
**File Synchronization**
The solution must incorporate a robust synchronization mechanism between the two files:
• When Power Apps records data in the XLSX file, those changes must be replicated in the XLSM file.
• When the XLSM file is updated—whether via macros or internal modifications—those changes must also be reflected in the XLSX file.
• Both files must remain synchronized at all times.
**Technical Controls and Error Handling**
The implementation must include technical controls designed to ensure the stability and reliability of the system:
• Robust error handling during synchronization processes.
• Prevention of update loops between the XLSX and XLSM files.
• Proper management of update events to prevent data overwrites or inconsistencies.
• Consideration of potential temporary file locks within SharePoint. • Ensure that the macros within the XLSM file remain unaffected by the synchronization process.
**Automatic XLSM Updates**
The XLSM file is updated periodically via macros. Any changes generated by these macros must also be reflected in the XLSX file to ensure that Power Apps always queries up-to-date information.
Similarly, information recorded in the XLSX file via Power Apps must subsequently be reflected in the XLSM file.
**Integration with Power BI**
In a later phase of the project, the existing visualizations from the XLSM file will need to be migrated to Power BI. It is important to clarify that this does not involve developing the dashboard from scratch, but rather replicating the visual structure and logic of the current Excel file within Power BI.
The objective is to build a Power BI dashboard that maintains a visualization equivalent to that of the XLSM file, while also allowing for the optimization of certain aspects regarding data analysis, visualization, and automation.
Furthermore, it is expected that data updates can be managed in an automated manner—potentially through Power Automate or other mechanisms available within the Microsoft ecosystem.
**Implementation Quality**
A stable, efficient, and well-structured solution is expected. The specialist must evaluate and propose technical alternatives if a more robust option exists for achieving the required synchronization within the SharePoint, Excel, Power Apps, and Power BI environment.
**Process Documentation**
The entire implementation process must be documented from the outset through technical notes and recordings of the development process.
The documentation must explain the implemented architecture, the logic employed, and the synchronization mechanisms, enabling PepsiCo's Supply Chain team to subsequently manage, maintain, and update the solution.
**Project Conditions**
If you are capable of implementing the requested requirements, the estimated budget for this implementation is 100 USD.
If you agree with the scope and conditions, we can begin immediately, as the implementation is required to be ready as soon as possible.
Additionally, upon the completion of this project, access will be granted to future projects related to automation and data analytics. This entails becoming part of our portfolio of contractors and the group of consultants with whom we work regularly within PepsiCo's Supply Chain area.
**Project Context**
We currently utilize an Excel file in XLSM format, which contains macros and operational logic used by the team. This file is stored on SharePoint and constitutes an integral part of the department's workflow.
To enable integration with Power Apps, it is necessary to design and build an architecture that allows for data entry via the application without compromising the functionality of the existing macros.
**Solution Structure**
The solution must incorporate the following elements:
• Maintain the original Excel file—including macros—in XLSM format as the primary file.
• Create a structurally identical copy of the file in XLSX format.
• The XLSX file will serve as the data source utilized by Power Apps.
• Both files will remain hosted on SharePoint.
**Integration with Power Apps**
It is necessary to implement the logic required to enable Power Apps to record or modify data within the XLSX file.
This will allow users to log hours or other operational events using buttons or forms embedded within the application. The XLSX file will function as an integration layer bridging the application and the XLSM file.
**File Synchronization**
The solution must incorporate a robust synchronization mechanism between the two files:
• When Power Apps records data in the XLSX file, those changes must be replicated in the XLSM file.
• When the XLSM file is updated—whether via macros or internal modifications—those changes must also be reflected in the XLSX file.
• Both files must remain synchronized at all times.
**Technical Controls and Error Handling**
The implementation must include technical controls designed to ensure the stability and reliability of the system:
• Robust error handling during synchronization processes.
• Prevention of update loops between the XLSX and XLSM files.
• Proper management of update events to prevent data overwrites or inconsistencies.
• Consideration of potential temporary file locks within SharePoint. • Ensure that the macros within the XLSM file remain unaffected by the synchronization process.
**Automatic XLSM Updates**
The XLSM file is updated periodically via macros. Any changes generated by these macros must also be reflected in the XLSX file to ensure that Power Apps always queries up-to-date information.
Similarly, information recorded in the XLSX file via Power Apps must subsequently be reflected in the XLSM file.
**Integration with Power BI**
In a later phase of the project, the existing visualizations from the XLSM file will need to be migrated to Power BI. It is important to clarify that this does not involve developing the dashboard from scratch, but rather replicating the visual structure and logic of the current Excel file within Power BI.
The objective is to build a Power BI dashboard that maintains a visualization equivalent to that of the XLSM file, while also allowing for the optimization of certain aspects regarding data analysis, visualization, and automation.
Furthermore, it is expected that data updates can be managed in an automated manner—potentially through Power Automate or other mechanisms available within the Microsoft ecosystem.
**Implementation Quality**
A stable, efficient, and well-structured solution is expected. The specialist must evaluate and propose technical alternatives if a more robust option exists for achieving the required synchronization within the SharePoint, Excel, Power Apps, and Power BI environment.
**Process Documentation**
The entire implementation process must be documented from the outset through technical notes and recordings of the development process.
The documentation must explain the implemented architecture, the logic employed, and the synchronization mechanisms, enabling PepsiCo's Supply Chain team to subsequently manage, maintain, and update the solution.
**Project Conditions**
If you are capable of implementing the requested requirements, the estimated budget for this implementation is 100 USD.
If you agree with the scope and conditions, we can begin immediately, as the implementation is required to be ready as soon as possible.
Additionally, upon the completion of this project, access will be granted to future projects related to automation and data analytics. This entails becoming part of our portfolio of contractors and the group of consultants with whom we work regularly within PepsiCo's Supply Chain area.