spreadsheetimporter/packed-deployment-abap
A UI5 application template containing nothing but the Spreadsheet Importer, deployed once to an ABAP server so other apps reference that copy instead of bundling the component each time.
Bundling ui5-cc-spreadsheetimporterui5-cc-spreadsheetimporterA UI5 component that adds a spreadsheet upload dialog to a Fiori elements or freestyle app and submits the rows it reads through the app's own OData model.community org, ui5 into every app that uses it means rebuilding and redeploying every app when a new version lands. This template packages the component as a UI5 app of its own, com.spreadsheetimporter.centraltest, and deploys it to an ABAP system through ui5-deploy.yaml and an .env file naming the target URL, client, app name and transport. The app it builds carries no business screens: what it shows is the deployment shape, not an upload, and the README expects you to copy the repository into your own git server so local deployments and upstream updates stay apart.
Facts
Where it sits
Who is behind it
In the atlas: maintains 9@spreadsheetimportermaintainerMarian ZeisContributes to this
In the atlas: maintains 35, contributes to 86, wrote 25@marianfoo1 contributor
What it declares
Every artifact
- Type
- Sample
- Origin
- By a community org
As a sample
- Form
- does not say
Connections
Getting files into tables and table content back out as files
Download
README
quoted from spreadsheetimporter/packed-deployment-abap under Apache-2.0, readUI5 Application com.spreadsheetimporter.centraltest
This UI5 Application enables a packaged deployment of the UI5 Spreadsheet Importer to use as central deployed component.
Description
Requirements
Either npm or yarn for dependency management.
You can use this concept in multiple ways:
- create your own app and use the same concept as here
- clone/fork the repo and change according to your needs
- use the app as is and only change config
Preparation
Use npm to install the dependencies:
npm install
Deploy the app
- change .env file to your needs
Copy the .envTEMPLATE and rename it to .env. Add your credentials to the file.
- Change the ui5-deploy.yaml file to your needs
Copy ui5-deployTEMPLATE.yaml file and rename to ui5-deploy.yaml and change the following values to your needs:
- target url
- target client
- app name
- app description
- app package
- app transport
- Deploy the app
Execute the following command to build and deploy the app:
npm run deploy
Update local deployed apps
It is recommended to start with this sample app to deploy the Spreadsheet Importer to your local server.
Using this app
When you executed the above steps, you can create a new app in your own git server.
Commit your changes (like the new deploy yaml) and then push to your git server.
If a new version of this app is available, you can update your local deployed app.
You then have to git remotes like origin and local.
When you want to update your local deployed app, you can execute the following command:
git pull origin main # pull the latest changes from the repo
npm install # install the latest dependencies including the newest versions of spreadsheetimporter
npm run deploy # deploy the app to your local server
git push local main # push the changes to your local git server
Only using this as basis
Alternatively you can use the node addNewVersion.js command to only update the relevant lines in the package.json and manifest.json files.
node addNewVersion.js
git commit -am "update version"
git push local main
License
This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
Contributors
History in the atlas
- First seen.
For your agent
- Ref
artifact:spreadsheetimporter-packed-deployment-abap- JSON
- /artifacts/spreadsheetimporter-packed-deployment-abap.json
- MCP
- Connecting an agent