Find Cycle Based on Date

[TerryR]

I want to use powerapps to identify the cycle in which a product was produced.  I have a separate table set up like this...

Cycle      CycleStartDate

162         2019-05-29

161         2019-04-17

160         2019-02-27

159         2018-12-11

For example, if the product was produced on 3/16/2019, the app needs to show that the product was produced in cycle number 160.  Any ideas on how to do that?

[RandyHayes]

@TerryR 

I would first put a label on your screen and set the text property to:

LookUp('[dbo].[CycleDates]',
       DateValue("7/22/2019") < CycleEndDate &&
       DateValue("7/22/2019") >= CycleStartDate
      ).Cycle_Number

Replace the hardcoded date with any value you know is valid. See if you get a value you expect or an error.

If you get an error, then I would remove your data source and then add it back in.  This all assumes that CycleEndDate and CycleStartDate are defined as Date fields in your table.

[TerryR]

It appears to me that the dates are not correlating between the one provided in the dte picker (or hardcoded in) and the date in the sql table.  When we set it up to look for the keyID = 21, for example, it pulls back the correct cycle, but not when we use date. Do the dates in the table and the target date need to be formatted the same?

When I put in DateValue("2019-05-29", "en-US") into the formula, the formula bar indicates that is equal to 5/29/2019m 12:00:00 AM.  The lookup table has dates formatted as 2019-05-29.

[TerryR · Accepted solution]

We finally got this working.  We had to change the date fields in the SQL lookup table to Char(10), then the formula below worked!

LookUp(CycleDataSource,(DateValue(CycleStartDate) <= DateValue2.SelectedDate) && DateValue(CycleEndDate) > DateValue2.SelectedDate, Cycle)

[RandyHayes]

@TerryR 

Gald you got it working.  However, there is no need to set those columns to char columns...the date fields and the comparisons work perfectly well and take less "processing" (in the sense of conversion formulas) to deal with.

So, if you come across it again, I would lean toward the data column before going with a text column.

[TerryR]

That's what I would prefer too, if I could get it to work!  It's working this way though, so I'm not to excited about reinventing the wheel after working on if for a month last time.  Maybe next time!  Thanks for supporting me through the problem.