Microsoft 1383
Dulce Donten
We have hosted a series of webinars on the SB 1383 Paper Procurement to help build understanding of the regulations, provide tips for implementation and build capacity of current or potential paper vendors working with cities in the County.
Disclaimer: The information contained herein shall not be construed as legal advice. Alameda County has compiled this information to support local government compliance efforts with SB 1383. The County makes no warranties and accepts no responsibility for compliance of other jurisdictions. Seek the advice of your legal counsel for questions regarding your jurisdiction's compliance efforts.
Currently running ACAD 2017 on W10 X64.
My Logitech M310 will NOT pan or zoom and I no longer want to try to fix this - tried everything over a period of a year and I am done with this mouse for CAD.
My backup mouse I am currently using is a Microsoft Model 1383 but pan and zoom wheel seems to be too "sensitive" and whenever I try to pan, it zooms all over the screen. Not sure if this is adjustable, but I am open for suggestions to make the Microsoft Mouse work better with ACAD. Currently it is tolerable but I can't fine tune it.
@JamesC007. Rob's post was great, but since he wrote it, a new "FormatNumber" option became available which makes things much easier. I've screenshotted the following from a real working scenario we use internally:
Then, in a For Each loop, increment the variable, and format using the Format Number action. Note the number format string is stored in the List, screenshot further down. (The Update Projects List Item just applies the current number to our separate project list)
Note that the way we do this is to store the next available number in our list, apply the next number, then increment afterwards.
Note, the reason we're not getting any infinite loops is that we only trigger this whole flow when an item (or file, depending on list or library) is created. It is important to not use the "Created or Modified" otherwise the action that updates the number on your target document or list item will continually fire...you could use a Trigger condition to resolve that, but it's easier to just use the "is created" trigger.
If you needed to apply an auto-number as a one off to a historical set of list items, then you could create a separate flow with a manual trigger that you only run once, that filters all your items/documents then uses a foreach to apply the above logic. In that scenario you would need to make sure you set your loop concurrency to 1 only, to allow the number to increment correctly.
We format our number as MTX21-0000, with 21 being the year. Ultimately, what I am attempting to do is make this as dummy proof as possible. So I would like to bring the last two digits of the year in automatically, as well as return back to 0001 as the first record of the year without interaction from a common day user. Can I incorporate that into the solution that you have posed?
I am fairly new to Power Automate as well as Power Apps, but I am attempting to learn this, which is why it took so long for me to familiarize myself with the Power Automate flow that was initially presented to get it to work mostly correct.
With that said, I think that the pictures you posted for your flow are out of order....correct? As you need to get the criteria first, which would be "when an item is created" in the log list. From there, you then "initialize the variable" and then "Get Items". Then onto "For each autonumber result" and "update autonumber list item". Am I understanding that correctly?
My list was created by importing a bunch of data from an Access DB (via Excel), and I wanted a new ID number that would start after the ID numbers from the data I had used - thus the 1383, which combined with the number of records, would mean that my next ID number would be 2001.
It worked. Until the next time I logged in, and all of the NewIDs across all records was 1383. So I edited the formulas, put brackets around ID, and it worked again. Until the next time I logged in, and all of the NewIds across all records was 1383. So I ... well, you get it.
@pjosifovic
I was never able to get the list to work appropriately as it would keep thinking that new items were created and renumber the entire list....over and over again. I ended up with 4000 runs within a matter of half an hour. But I did manage to have it include the year using the column from the sharepoint list that is the Date Created column, I extracted the year within the sharepoint list and formatted it in another column to just display the last two numbers. Then I included that as part of the log number.
Power Business Intelligence (Power BI) is a business analytics and data visualization tool developed by Microsoft. Power BI offers a user-friendly interface for data modeling. The core strength of Power BI lies in its rich visualization capabilities displayed within its reports. It allows users to:
The excel reports below contain exported data from the individual pages of the Power BI reports. They are separated and titled by the corresponding page within the Power BI reports. These excel sheets are customizable after they have been downloaded.
Within this Power BI report, the user can find data about collection systems that satisfy SB 1383 requirements. The user can filter results using a drop-down menu by individual jurisdiction, regional agency, county, and jurisdiction. If not filtered the report will automatically display all results.
Within this Power BI report, the user can find data about types of recycled products being procured and diverted by California jurisdictions as well as different ordinances, and source reduction and recycling element (SRRE) programs being implemented within jurisdictions. The user can search this report by a specific jurisdiction, regional agency, or county. The user can search by a specific procured product, material, ordinance, or SRRE program.
Within this Power BI report, the user can find data about facilities, organic waste haulers, education and outreach, and contamination monitoring. The user can search this report by a specific jurisdiction, regional agency, or county.
On October 26th, 2021, CalRecycle hosted a statewide webinar that provided an overview of changes to RDRS reporting requirements pursuant SB 1383. The webinar highlighted the entities and data required to be reported via RDRS to comply with SB 1383 regulations regarding organic material recovery. This reporting will commence with the first RDRS reporting period for Transfer/Processors starting May 1, 2022, and every reporting period thereafter. For a list of all due dates, review the RDRS Reporting Schedule.
These guidance tools were developed by CalRecycle as a courtesy for informational and example purposes only. Use of these tools is optional and is not a regulatory requirement. In the event of any conflict with these guidance tools or information herein, applicable statutory and regulatory provisions shall control. These tools and information herein are based on known facts and legal authority as understood by CalRecycle at the time of release. Any analysis, guidance, or other information herein may be subject to change based on changed facts or legal authority, actual or understood, subsequent to the publishing of these tools. The provision of these guidance tools and any analysis, guidance, or other information herein shall not be construed as a waiver of any rights or remedies available to CalRecycle. Users are encouraged to seek the assistance of legal counsel to comply with applicable state law based on their pertinent facts and circumstances. CalRecycle makes no representation that use of these tools will ensure compliance with regulatory requirements. The user assumes all risk and CalRecycle accepts no responsibility or liability to any person because of the use of, or reliance upon, these tools or the information herein.
The State of California has set an ambitious goals for recycling, composting and source reduction of solid waste. To help reach these goals, the State has adopted Assembly Bills 341 and 1826 and SB 1383. AB 341 is a Mandatory Commercial Recycling bill, AB 1826 Mandatory Organic Recycling and SB 1383 provides education and outreach regarding organics recycling and edible food donation. Please visit the following links for additional information on this important legislation.
Constantine L. Trela, Jr., Sidley Austin, LLP, of Chicago, IL, argued for defendant-appellee. Of counsel on the brief were William A. Sankbeil and Fred K. Herrmann, Kerr, Russell and Weber, PLC of Detroit, MI.
The appellant in Ultra-Precision also appealed the district court's ruling denying its claim for correction of inventorship. 411 F.3d at 1376. We affirmed the district court's judgment on that issue. Id. at 1383.
We note that, in determining whether federal question jurisdiction exists, the Supreme Court has held that " [o]ne corollary of the well-pleaded complaint rule ... is that Congress may so completely pre-empt a particular area that any civil complaint raising this select group of claims is necessarily federal in character."Metro. Life Ins. Co. v. Taylor, 481 U.S. 58, 63-64, 107 S. Ct. 1542, 95 L. Ed. 2d 55 (1987). Thus, in some instances, an area of law is so clearly and completely preempted that a complaint in such an area of law may present a federal question even though it raises only state law causes of action. See, e.g., id. at 67, 107 S. Ct. 1542 (holding claims within the scope of section 502(a) of ERISA completely preempted); Avco Corp. v. Aero Lodge No. 735, Int'l Assoc. of Machinists and Aerospace Workers, 390 U.S. 557, 560, 88 S. Ct. 1235, 20 L. Ed. 2d 126 (1968) (holding claims within the scope of section 301 of the LMRA completely preempted). Thompson's claim is not within the scope of such an area of law. See Bonito Boats, Inc. v. Thunder Craft Boats, Inc., 489 U.S. 141, 152-57, 109 S. Ct. 971, 103 L. Ed. 2d 118 (1989) (recognizing that the broadest reading of its precedent on the preemptive effect of federal patent law "would prohibit the States from regulating ... the tortious appropriation of private information" and rejecting such an "ipso facto preemption" reading of federal patent law).
c80f0f1006