I am attempting to do historical analysis of call stats, the obstacle I am facing is that my agent's have the option of changing positions. For example Front/Back office, I would like to be able to differentiate their stats by role per year. If a front office agent is in front office from January to march, but then gets promoted to back office in April; I would like to time stamp their stats or perhaps create a table that references their time in that role to make sure the stats I am looking at are historically accurate. Currently I am using stats on a excel workbook and using power bi to visualize the stats year to date, and month over month. Right now I am encountering the fact when an agent's role changes their historical stats gets moved to their new position. I'm open to any suggestions or logic.
Related
could please someone enlighten me?
I have a data set and I need this data set to be refreshed on the 5th and 15th of the month.
But there can only be one schedule per Cognos object, right?
Is this the optimal solution?
I setup a schedule on the data set itself for the 5th of Month.
Then I create a job and add that data set as a job step.
I schedule the job containing that data set (which includes its own schedule) for the 15th.
What happens on the 15th and how these two schedules work with each other?
(This could also apply to reports etc).
Many thanks
I went through the documentation and some online articles, but there is no definitive answer if a data set (or a report..) can have multiple schedules set.
Lots here about reports and report views explaining how I handle schedules. Substitute "dataset" and "job" and I think you'll get what you want.
One schedule per object leads to limitations. I have found for reports that it is better to create a report view to handle the schedule. I very rarely schedule a report anymore because I often end up needing more than one schedule or set of parameters.
Using a report view provides a means to not only create multiple schedules per report, by creating multiple report views, but also have those schedules send the reports based on independent sets of parameters. For example, the regional VPs want reports showing their sales revenue for the month, but only for their regions. I would create one report, then create a report view for the U.S. and a report view for Europe. Both get sent on the 5th of the month.
Likewise, I could set up 2 report views to work around the scheduling limitations. Say I want to send the same report on the 5th and the 15th. I would create the report, then create 2 report views to handle the schedules.
So, to translate this to your need...
To refresh the same dataset on the 5th and the 15th, create 2 jobs that have the dataset as a step -- one job for each schedule.
Using jobs looks like the right thing to do for your use case. I don't see another scheduling option for datasets.
I have an access database in which multiple customers will be placing large orders on a weekly basis. I have a query automatically set up in excel to refresh the information every minute. A potential issue I could see happening: Manager places order in our access form, decides to edit his record later w/o contacting the scheduler, and changes the order information he originally entered. I would like to track what it was changed from and to, as well as the date they changed it. These orders have to be placed by a certain time in the week for them to make the shipment in or out the following Monday. If orders are changed, I want to know. If orders are changed after the deadline, I especially want to know. Thanks
Create a before update event that inserts the changes into an audit log table. Here is the resource I used for my databases: https://www.techrepublic.com/article/a-simple-solution-for-tracking-changes-to-access-data/
Note: This will only track changes made to existing records through the form. It also will not track deletions or changes made directly in the table.
We are trying to write customization to generate a download GL account summary information from Acumatica to text file. Need to be able to calculate period summary information (beginning balance, net change, and ending balance for each account using code. I'm assuming that Acumatica has an object to calculate those values for a specific Financial Period ID...but I dont know what it is. Can anyone help?
The information you're looking for is already stored in the GLHistory table. The data is aggregated by ledger, branch, financial period, account and subaccount. This information is updated by accumulator attributes that are used during the GL release process.
I would like to premise that I am not a coder, and have limited SharePoint experience. Nonetheless, I have a task at work to create a new tool for a group at work. This tool will allow them to track things through its life-cycle. The old tool will stop being used once they hit the 49,999th record. At that point we will transition to SharePoint. The prior numbers will live with those records and we will be unable to start back at the number 1.
My goal is to have an ID field for each record that incrementally grows starting from the number 50,000.
I tried creating a new calculated formula field that does 50,000 plus the ID but it does not work effectively. There tends to be a lag. The lag can be anywhere from 5 minutes to a day or two. In turn, I need an alternative option.
With a friends coaching, I am messing with SharePoint designer to automatically create a record once one is deleted and delete one every time one is created. However, this times out occasionally. Even more so, it is extremely slow. It will take me a week or so to get to 50,000. Does anyone have any experience or expertise to assist me? It is very appreciated.
The way I did it was to create another field and used that in all my views. Update it through a SharePoint Designer workflow on create - set the field to ID+50000, for example, or whatever you need. Maybe give it a bit of a buffer and set it to ID+51000. By the time the workflow is running the ID has been created and you can use it in a workflow.
If you are going to be moving your old records to the list, you can change the workflow to only update the new field if it's blank. That way you can save the original ids.
My boss has recently tasked me with developing an estimating form in Dynamics CRM Online for use by his sales team. The idea is that his sales team can enter the parameters into a dialog and have Dynamics spit out a rough estimate for the cost of the project. Sales team members need to be able to do this while on site at a customer's location.
I have no idea about anything with Dynamics. I could easily do this in Excel VBA and make it look nice. I could develop my own app in C# or Java. But the ideal is to integrate this into Dynamics CRM with existing opportunities and associated tools. I've looked at Dynamics on my boss' monitor and I've poked some of the existing dialogs on our old on-premises Dynamics server with a long stick.
Is this kind of application even possible with Dynamics Online? We'd need to take user input, query the product database for pricing info from that input, and do some fancy arithmetic to spit out a number and ideally save the data in some way associated with an opportunity. This is a flooring company, and I envision an estimating tool where you can dynamically add a room to a list in a dialog, specify the size of the room in two text entry boxes (length x width), and select a type of flooring and substrate from a combination of radial buttons and drop down boxes, and finally have a price displayed for that room with a cumulative price displayed for each additional room added to the list.
Somebody please tell me if this is possible and where I can go for some resources on developing for Dynamics CRM to teach me how to do it. Help!
:edit:
Essentially the current manual estimating process is rather laborious and takes a couple of days turnaround. Sales reps run through a checklist and submit a form to the office with information about the size of the job, substrate, and the products to be installed and then a human operator manually calculates an estimate with that information. An automated system should allow sales reps to input some basic information and get a rough estimate in minutes while on site with the customer making the sale.
At its most basic, the application must be able to accept user input for the substrate under the flooring, the new flooring type, and square footage for each type of flooring. With that information, it needs to query price information from a database and then calculate an estimate for the project. It needs to be available online via mobile devices (tablets or possibly phones) for sales reps who are on location with a customer.
Beyond that, if we can have it save the estimate into an existing opportunity or create a new opportunity within Dynamics CRM, that would be great.
To avoid learning specific CRM development features, you can add web resource, it could be HTML page, add link to the web resource on CRM page and using only javascript populate field you need with any data you need.
This could definitely be accomplished with the out-of-the-box features. It wouldn't work exactly like you envisioned, but it would be close.
You'd need to set up the Product Catalog in CRM. Each Product could be one of your flooring types or substrates. The Pricing List for each Product would show how much 1 square foot of each type of flooring costs.
When Sales creates an Opportunity, they can add Product Line Items for each different type of flooring, along with a Quantity (which would be total Sq Feet for that item). CRM would then calculate the Line Item and the total Opportunity from the Price List and Product Catalog. Each line item total can also be discounted or overridden from the Price List, if necessary.
Once the customer wants a Quote, you can convert the Opportunity into a Quote, and all line items are copied over. You could then print this out and give it to the customer.
If the customer accepts the Quote, you can convert the Quote into an Order. Again, all line items are copied over.
Finally, you can create multiple invoices for an Order, and again line items are copied over and you can override prices or line items if necessary for billing.
There are lots of good video tutorials out there on setting up the Product Catalog, Price Lists, Discount Lists, etc. Hope that helps!