What will be the ccm query to List the revision or commits that have been made between two dates provided?
Related
I have made table as follows (https://apexinsights.net/blog/convert-date-range-to-list):
In this scenario suppose I configure Incremental refresh on the Start Date column, then will Power BI support this correctly. I am asking because - say the refresh is for last 2 days or last 2 months, then it will fetch the source rows, and apply the transform to the partition. But my concern is that I will have to put the date param filter on Start date prior to non folding steps so that the query folds (alternatively power query will auto apply date filter so that query can fold).
So when it pulls the data based on start date and apply the transforms then I'm not able to think clearly about what kind of partitions it will create. Whether it is for Start date or for expabded date. Is query folding supported in this scenario?
This is a quite complicated scenario, where I would probably just avoid adding incremental refresh.
You would have to use the RangeStart/RangeEnd parameters twice in this query. Once that gets folded to the data source to retrieve ranges that overlap with the [RangeStart,RangeEnd) interval and a second time after expanding the ranges to filter out individual rows that fall outside [RangeStart,RangeEnd).
I'm attempting to write a formula for excel that will look at 3 different columns of data in a query table that I'm pulling from my teams sharepoint site. I'm trying to have a Yes/No result given.
The formula I've written so far is
=IF(AND(ISTEXT(Governance_Master_List__2[Is the check c]="Yes")+(AND(ISTEXT(Governance_Master_List__2[Merged Month and Year Due]="January 2023")+(AND(ISTEXT(Governance_Master_List__2[Frequency]="Weekly")))))),"Yes","No")
So, In this example I want the formula to look at [Is the check c] for a "Yes", then Look at the [Merged month and year due] for January 2023, and then look at [Frequency] for "Weekly", and if all 3 of those are met to show the result of Yes onto another worksheet.
So far the formula isn't throwing an error when making it, but it only returns the No result, even when I ensure that all the Weekly, January 2023 entries are showing as Yes.
I'm very new to excel in terms of formulas and am learning as I go. I feel like, because the refernce query table i'm looking at has tons of different values (eg, the frequency has weekly, 6 monthly, monthly, quarterly etc and that there are 12 months to choose from) that the formula is stopping because its looking at and not ignoring those other options, hence the constant false result.
I've tried the following variations with no result..
=IF(AND(ISTEXT(Governance_Master_List__2[Is the check c]="Yes")(AND(ISTEXT(Governance_Master_List__2[Merged Month and Year Due]="January 2023")(AND(ISTEXT(Governance_Master_List__2[Frequency]="Weekly")))))),"Yes","No")
=IF(AND('Imported data'!C1:C200="Weekly")+(AND('Imported data'!E1:E200="January 2023")+(AND('Imported data'!H1:H200="Yes"))),"Yes","No")
=IF(AND('Imported data'!C1:C200="Weekly")(AND('Imported data'!E1:E200="January 2023")(AND('Imported data'!H1:H200="Yes"))),"Yes","No")
The output excel sheet is to show our quarterly compliance reporting, i'm simple trying to automate the process of entering the data into that report, as the teams use a sharepoint list to enter their compliance tasks.
Anyone have a suggestion on how I can get this working? Eventually it'll be used to populate a number of different yes/no report cells based on the relevant month and frequency of the check.
Relative Novice with PowerBI. I have a Table visualization that pulls from several SharePoint lists and summarizes actions for audit report recommendations. Most recommendation actions are completed on a single date so have a single Date Completed entry, but some recommendations require more than one action over time so have multiple Date Completed entries. I would like my PowerBI Table to only show the most recent Date Completed for any Final Report Recommendations with multiple Date Completed entries (and just the one date for Final Report Recommendation with only a single Date Completed entry). Here's the problem, however: The Final Report Number entry is taken from a SharePoint List called 'Audit Cases' and the Rec Number is taken from a SharePoint list called 'Recommendations' while the Date Completed is taken from a SharePoint list called "Follow Up Journal'. The attached image shows a part of my Table as it currently displays - you can see the multiple entries for Report GAO-20-110 Rec Numbers 11 & 12. I would like the Table to only show the most recent entry for those Recs, for instance: only 1/4/2022 for Rec 11. I've tried some measures in this forum for Max Date, etc. but they don't seem to work when the Report and Recommendation and Completed Date info is pulled from different tables. Any thoughts? Thanks in AdvanceTable Example
You can right-click on the date column in Values and choose Latest.
I have a dates tables, columns:
date: the date e.g. '2018-06-29'
business_day: 1 or 0 to indicate if date is business day or not
I want to create a User-Defined function in Redshift that outputs between two dates how many business days. In a select statement is will look like :
select business_days(start_date timestamp, end_date timestamp) as integer
for example:
2018-06-29 is a friday business day
2018-06-30 saturday non business day
2018-07-01 sunday non business day
2018-07-02 business day
select business_days( '2018-06-29', '2018-07-02') should output 2
Redshift does not allow aggregates inside a function and I am looking for a workaround.
Amazon Redshift User-Defined Functions cannot access the network, nor can they access data stored in tables.
As an alternative approach, you could create a Python function that can calculate the difference between two dates.
If you merely wish to skip weekends, you could Count number of days between dates, ignoring weekends.
If you have more complex logic, such as skipping holidays that vary by year, you will need to supply that information to the Python function, such as including the special dates within the function itself (eg in a list of holiday days).
I'm keeping track of machines & their on/off status, and their service history:
MachineHistory
MachID
Branch
Status
StatusDate
ServiceHistory
ServiceID
MachID
ServiceDate
Calendar
Date
Year
Month
MachineHistory and ServiceHistory are related on MachId.
Calendar is related to both on the date cols.
What I want is measures for ActiveMachineCount (means Status = "ON") and ServicedMachineCount (means row exists in ServiceHistory table). Both should be group-able by date & branch.
So I should be able to have an excel pivot that shows eg
Branch ActiveMachCnt ServicedMachCnt
A 50 13
B 23 6
I have a measure of MachIdCnt = distinctcount(machineid)
My problem is with ActiveMachIdCnt = calculate([MachIdCnt], MachineHistory[Status] = "ON")
No matter how I try to fiddle with ActiveMachIdCnt, I either get a) literally ALL of the machine id's in the table, or b) a count of machine id's that have been serviced (due to relationship).
I'm clearly not understanding the ALL, ALLEXCEPT, etc family of functions correctly. :/
How can I get the ActiveMachIdCnt measure to "ignore" the relationship to ServiceHistory, but still respect filters on date & branch?
Thanks for any tips,
sff
I think you are having this problem because your data model is incorrect. Your history tables (machine history and service history) BOTH are fact tables. Fact tables can not have direct relations, it's prohibited.
What you need to do is to add a dimension "Machine", which will contain MachineId and other usefull attributes of your machines. This table then will be related to Machine history and Service history via MachineID, exactly the same way as your Calendar table is related to them via Date.
With such structure, your DAX is very simple:
Active Machines = DISTINCTCOUNT(MachineHistory[MachineId])
Serviced Machines = DISCTINCTCOUNT(ServiceHistory[MachineId])
and if you want to analyze these measures by Branch, you will need to have branch either as a separate dimension (that would be my choice), or as an attribute in the dimension "Machine" (which would work but conceptually is an inferior design).