# Replacing a weekly email with perspective pages

**URL:** <https://forum.inductiveautomation.com/t/replacing-a-weekly-email-with-perspective-pages/47843>\
**Category:** Ignition\
**Created:** [June 16, 2021, 4:29pm UTC](https://forum.inductiveautomation.com/t/replacing-a-weekly-email-with-perspective-pages/47843 "2021-06-16T16:29:33Z")\
**Posts on this page:** 9\
**Page:** 3

<div class="post-metadata">

**Author:** ![zacharyw.larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zacharyw.larson/32/23749_2.png) [@zacharyw.larson](https://forum.inductiveautomation.com/u/zacharyw.larson)\
**Post date:** [June 23, 2021, 7:20pm UTC](https://forum.inductiveautomation.com/t/replacing-a-weekly-email-with-perspective-pages/47843/41 "2021-06-23T19:20:54Z")

</div>

Now I just need that elective studies thing for perspective, except 4 hours of tables and database manipulation instead haha

---

<div class="post-metadata">

**Author:** ![matthew.ayre](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matthew.ayre/32/19499_2.png) [@matthew.ayre](https://forum.inductiveautomation.com/u/matthew.ayre)\
**Post date:** [June 24, 2021, 7:03am UTC](https://forum.inductiveautomation.com/t/replacing-a-weekly-email-with-perspective-pages/47843/42 "2021-06-24T07:03:44Z")

</div>

Unfortunately, nothing beats getting wrong 50 times before finding the right solution 😃

> [@zacharyw.larson](#):
>
> there will be a bunch of database work

This would definitely be the first step for me, get the DB structure in place then focus on how to get it in there.

> [@wking](#):
>
> I use… single row selection… then ill make a button visible if they select a row… if the selection == None the button is invisible…

This is how I do the table manipulation as well. For example:

 ![Screenshot_20210624-075343_Ignition Perspective](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/8/e8f15ddfd0c7e082bc788509bb3c13375d679583.jpeg) ![Screenshot_20210624-075525_Ignition Perspective](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/a/5abb4b1c2a6841835f1e3a6020992aae447a981a.jpeg)

---

<div class="post-metadata">

**Author:** ![zacharyw.larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zacharyw.larson/32/23749_2.png) [@zacharyw.larson](https://forum.inductiveautomation.com/u/zacharyw.larson)\
**Post date:** [June 24, 2021, 1:00pm UTC](https://forum.inductiveautomation.com/t/replacing-a-weekly-email-with-perspective-pages/47843/43 "2021-06-24T13:00:23Z")

</div>

How do I set a status value of down for line 1 shift 2 for next Wednesday?  
How do I then call to see what the status is for the 1st thru 3rd shift?

I get how to use the tag historian on the past. I don’t know how to set tag values in the future though.  
Is there a scheduling component?  
I didn’t see a section of videos on scheduling.

---

<div class="post-metadata">

**Author:** ![zacharyw.larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zacharyw.larson/32/23749_2.png) [@zacharyw.larson](https://forum.inductiveautomation.com/u/zacharyw.larson)\
**Post date:** [June 25, 2021, 6:17pm UTC](https://forum.inductiveautomation.com/t/replacing-a-weekly-email-with-perspective-pages/47843/44 "2021-06-25T18:17:17Z")

</div>

rewatching the sql section

---

<div class="post-metadata">

**Author:** ![zacharyw.larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zacharyw.larson/32/23749_2.png) [@zacharyw.larson](https://forum.inductiveautomation.com/u/zacharyw.larson)\
**Post date:** [June 30, 2021, 2:33pm UTC](https://forum.inductiveautomation.com/t/replacing-a-weekly-email-with-perspective-pages/47843/45 "2021-06-30T14:33:29Z")

</div>

I am still stuck on what is best to do for this.

Am I to make an sql table and put in every shift for the next two years?

---

<div class="post-metadata">

**Author:** ![matthew.ayre](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matthew.ayre/32/19499_2.png) [@matthew.ayre](https://forum.inductiveautomation.com/u/matthew.ayre)\
**Post date:** [July 1, 2021, 7:33am UTC](https://forum.inductiveautomation.com/t/replacing-a-weekly-email-with-perspective-pages/47843/46 "2021-07-01T07:33:18Z")

</div>

I may get some time tonight (UK time) to go through this in a bit more detail. However, it’s back to legacy SCADA systems (which shall not be named here for fear of getting stoned to death 😆) for me today 😓

---

<div class="post-metadata">

**Author:** ![victordcq](https://avatars.discourse-cdn.com/v4/letter/v/f6c823/32.png) [@victordcq](https://forum.inductiveautomation.com/u/victordcq)\
**Post date:** [July 1, 2021, 8:34am UTC](https://forum.inductiveautomation.com/t/replacing-a-weekly-email-with-perspective-pages/47843/47 "2021-07-01T08:34:48Z")

</div>

ive not really worked with shedules, but my guess is you will need a db of sorts (could be a big dataset tag too i guess) to store in special dates/shifts that do not follow the normal trends.

And then for every date that is not in the database you use a default template or so in your ui/logic

---

<div class="post-metadata">

**Author:** ![zacharyw.larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zacharyw.larson/32/23749_2.png) [@zacharyw.larson](https://forum.inductiveautomation.com/u/zacharyw.larson)\
**Post date:** [July 15, 2021, 7:51pm UTC](https://forum.inductiveautomation.com/t/replacing-a-weekly-email-with-perspective-pages/47843/48 "2021-07-15T19:51:56Z")

</div>

I appreciate the help on this.

It has been put on the back burner for a while. I have a few projects ahead of it, so right now I am at least 3 weeks from getting back to this.

There is kind of a canned solution coming to me from a third party, but then also I wanted to make this customizable option. Just don’t have the time for a while.

that is a really handy set of ideas about handling a template and handling special dates separately

---

<div class="post-metadata">

**Author:** ![zacharyw.larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zacharyw.larson/32/23749_2.png) [@zacharyw.larson](https://forum.inductiveautomation.com/u/zacharyw.larson)\
**Post date:** [October 27, 2023, 5:00pm UTC](https://forum.inductiveautomation.com/t/replacing-a-weekly-email-with-perspective-pages/47843/49 "2023-10-27T17:00:26Z")

</div>

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/f/1fded32feddbf110aeac8516851ca421eaf094ed.png)  
Sample Example

This might be coming off the backburner to the front for me.

Problem:  
I have a branch location that is emailing a spreadsheet schedules.  
One person has access to edit it, and they edit it in excel.

So I need a way to restrict access via scripting, which I think I can do.  
I could just put a pass code to access the page with a script.

Then, I need a way to make a table functionally similar to Excel editing while also updating the database with each change.  
**How do I do that?**

[Previous page](https://forum.inductiveautomation.com/t/replacing-a-weekly-email-with-perspective-pages/47843.md?page=2)
