AndreaJohannes
Qrew Trainee
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: using a list-user field to filter a report
Hi Mark, yes, it does have a filter option for includes current user. I've tried that as well and run into the same issues as I do when using the "is equal to" filter. When I use includes, all areas accounts and categories show up when I test as a specific user. Andrea ------------------------------ Andrea Johannes ------------------------------using a list-user field to filter a report
Howdy, I posted recently about a budget app I am working on. I have Areas. Areas have many accounts. Each account can have many categories. Each Area/Account/Category combination can have many expenses. I also have budget administrators. These budget administrators can have more than one area that they are responsible for. I've got the conditional drop downs working so that when a specific area is chosen, based on that area there is a specific list of accounts and based on the area/account combo chosen, there is a specific list of categories to which expenses can be added. Where I am stuck is that I want my budget administrators to only be able to see and/or edit/add expenses to those areas that they have been "assigned" to. It was suggested that I use a list - user field, which I have done on the area table. The area and the admin flow as a lookup to the Account table and then on down to the Category table as a look up. When I created the report for the home page and then tested as a user, the report didn't bring in any of the areas and I could see all of the accounts regardless of area. I'm not sure if it's an issue with how I'm creating the filter on the report maybe? I've tried many variations and just can't seem to get it to work. I've attached a picture of the filter, how I'm grouping the report, as well as the result I'm getting when I go to the home page and test as a specific user. (When I just run the report as a specific user, I get no results). I thought about basing the report off of the expense table -- but that report will only show me areas/accounts/categories where there is already an expense. I need the report to show all accounts, even if there is no expense yet, so I can add an add expense button. This will make it so that the admin will only see their accounts and when they click "add expense", the correct area will already be populated and kick off the cascading dropdowns for account and category. Thanks for your help and guidance! ------------------------------ Andrea Johannes Associate Director Texas A&M University ------------------------------Conditional Dropdowns, Cascading Dropdowns and Cascading Permissions
Howdy, I have a budget application. In my budget application, I have Budget Areas, Accounts, Categories, and Expenses. I also have employees/budget managers. Basically, I want my budget managers to enter expenses on the expenses form. When they click on Area, I want them to see only areas that they are assigned to. Then, based on what area they choose, they can pick from a list of accounts. Based on the budget manager/area/account relationship, they see a limited number of categories. I think I probably need to add some sort of many to many assignment table. So for example, Mike is the budget manager for both Business Solutions and Administrative Services. When he goes to enter Expenses, he should only be able to see these two areas. Then, based on which area he sees, he will pick from a specific list of accounts related to that area and a specific set of categories that are related to that area/account combination. I've tried following the instructions for cascading dropdowns, as well as creating the "assignment" relationship and following the instructions in the Cascading Permissions videos and can't quite get the limitations to work the way I would like. I'm not sure if I need to do something with formulas or if I'm just haven't cascaded the correct lookups and/or using the correct reference/proxy fields in creating the conditional dropdowns. The employee in the employee table is a user field as I was hoping to be able to use that in the roles to limit areas, etc. I've attached the current structure -- Any suggestions are welcome. Thanks! Andrea ------------------------------ Andrea Johannes ------------------------------Re: Need to create a date based reminder
Thank you Paul! I was able to create a field using that formula and it's working great. Now I need to be able to send an email to the email address in the superivsor email field. The reminder won't let me do that - and the notification requires something to happen to the position record in order to fire. Is there another way to generate that email to the email address in the supervisor field other than using reminders or notifications? ------------------------------ Andrea Johannes ------------------------------Re: Need to create a date based reminder
Hi Paul, Thanks for responding! Would that be a separate field that I am creating and that is what I would use? or is that something I would embed in either the notification or reminder? ------------------------------ Andrea Johannes ------------------------------Need to create a date based reminder
Hello, I have a start date field in my Position table. I need to create a reminder that sends an email to the email address in the Supervisor Email Address field 30 days before the start date in the current year to remind them to complete and submit an annual evaluation. I can't figure out how to write a formula to calculate the number of days from the start date, but in the current year. Also, I'm finding that the reminders won't allow me to pull in the Supervisor Email Address -- while a notification will only fire if the position is added or modified, which wouldn't be the case in this situation. Suggestions on how I might accomplish this? Do I need to parse the date into separate fields like month and day and then try to create the same month and day but with the current year? If so, how do I do that? Thanks in advance for any help/advice! ------------------------------ Andrea Johannes ------------------------------Use a Connected Table to populate a Request Table and making those fields non-editable once the Request is saved
Howdy, We keep all of our student employee information in a Personnel application. I am trying to create an application for my hiring managers to submit a request for a merit increase. In the Increase app, I have created an employee table connected to the Personnel table that holds the current information about each employee and their position. The connected employee table has a one to many relationship with the request table. (This allows my hiring managers to just select an employees name when submitting a request and it pulls in all of the current information such as position, position start date, current salary, effective date of current salary). They then fill out the rest of the request with the requested salary, requested effective date, etc. I also need for them to attach a copy of the employee's review. My team then reviews the requests, approves it, submits it into Workday (our University payroll system) and then updates the Personnel app to show that employee's new salary for that position. I've created a couple of checkboxes to show when the request was submitted in Workday and when the employee was updated in the Personnel application. Once complete, the review and request are printed and placed in the employee's personnel file. Unfortunately, the way our workflow works, once my team member has updated the information in the personnel app, when she goes back into the request to check that it's been updated (which effectively removes it from her todo list) and print the request, the request now has the new salary as the current salary (so it looks like nothing has changed). Is there a way to make it so that once a new request is submitted and saved those fields being populated by the connected table are no longer updated? Just making them read only does not do this. The other thing I thought about/tried was creating a "Submitted Request" table with an automation - so essentially when a new request was saved, it copied the values in the Request table over to the Submitted Request table. That way the current salary as of the time of request didn't change. My team member then updated the submitted request with approval, notes, submitted in workday, updated personnel app etc. My challenge with that is in relating whatever document was submitted on the initial request so that it showed up on the submitted request. I want my hiring manager to be able to initiate a request and add a document without having to go back out of that initial request and look up the submitted request. Kind of stuck at the moment, looking for suggestions. Thanks so much in advance for any advice! Below is my current structure for reference... ------------------------------ Andrea Johannes ------------------------------Use a Connected Table to populate a Request Table and making those fields non-editable once the Request is saved
Howdy, We keep all of our student employee information in a Personnel application. I am trying to create an application for my hiring managers to submit a request for a merit increase. In the Increase app, I have created an employee table connected to the Personnel table that holds the current information about each employee and their position. The connected employee table has a one to many relationship with the request table. (This allows my hiring managers to just select an employees name when submitting a request and it pulls in all of the current information such as position, position start date, current salary, effective date of current salary). They then fill out the rest of the request with the requested salary, requested effective date, etc. I also need for them to attach a copy of the employee's review. My team then reviews the requests, approves it, submits it into Workday (our University payroll system) and then updates the Personnel app to show that employee's new salary for that position. I've created a couple of checkboxes to show when the request was submitted in Workday and when the employee was updated in the Personnel application. Once complete, the review and request are printed and placed in the employee's personnel file. Unfortunately, the way our workflow works, once my team member has updated the information in the personnel app, when she goes back into the request to check that it's been updated (which effectively removes it from her todo list) and print the request, the request now has the new salary as the current salary (so it looks like nothing has changed). Is there a way to make it so that once a new request is submitted and saved those fields being populated by the connected table are no longer updated? Just making them read only does not do this. The other thing I thought about/tried was creating a "Submitted Request" table with an automation - so essentially when a new request was saved, it copied the values in the Request table over to the Submitted Request table. That way the current salary as of the time of request didn't change. My team member then updated the submitted request with approval, notes, submitted in workday, updated personnel app etc. My challenge with that is in relating whatever document was submitted on the initial request so that it showed up on the submitted request. I want my hiring manager to be able to initiate a request and add a document without having to go back out of that initial request and look up the submitted request. Kind of stuck at the moment, looking for suggestions. Thanks so much in advance for any advice! Below is my current structure for reference... ------------------------------ Andrea Johannes ------------------------------
