85829efd1d
WARNING! Do not assume the Excel file in this repo matches the VBA in the repo. The decision was made to use Teams for managing changes to the Excel tamplate because Git is ill-suited for binary files. The Excel file will be updated from time to time, but only when something major happens with the application as a whole. 1. Use the sheets' codenames to refer to them in code. This prevents breakage if the user changes the sheet name while working with the workbook. 2. Give the pivot tables proper, if not descriptive, names. 3. Simplify the code that detects a double-click in the pivot table. 4. Remove Windows_API as it was not being used. 5. Pare down TheBigOne to just the essential functions in Utils. 6. Refer to the data sources for the userforms' listboxes by using the worksheet.ListObjects collection. |
||
---|---|---|
build | ||
inquirey | ||
offline | ||
route_sql | ||
VBA | ||
.env.sample | ||
.gitignore | ||
columns.md | ||
create_certs.sh | ||
forecast_api.service | ||
index.js | ||
LICENSE | ||
Master Template.xlsm | ||
msauth.html | ||
package-lock.json | ||
package.json | ||
README.md | ||
sample_request.json |
This will not work without exactly the right database schema which is out of scope. this is only the running process part of the forecast.
Setup
- git clone (to //opt for verbatim use of the .service file)
npm install
- create certs:
chmod 700 create_certs.sh
,./create_certs.sh
- clone sample env
cp .env.sample .env
and specify 1) database creds 2) working directory 3) listening port - run:
node index.js
- navigate to
https://localhost:8080/
to valide it's connectable - open the spreadsheet and specify the target connection
additionally, to setup as service
- copy .service file to //etc/systemd/system/ (adjust user/working direct if needed)
sudo systemctl enable forecast_api.service
Initial Forecast
- all SQL depends on unchanged core sales matrix table schema